docs(research): record attended Windows broker failure

[hcoona]

Summary

Record the accepted preparation and explicitly attended interaction under PR #50. The action found one exact account match, then returned unknown_broker_error with broker status Unexpected and code 2147786073 (0x80049D59) in about 20.6 seconds. No token result, authenticated Git request, or reuse follow-up occurred. The operator saw the input form and a brief possible WAM surface; the failure cause remains unresolved.

Authorization and Governing Records

Issue #35 and the accepted Delivery Wave at facfec1aa86b88601a9a9e7835bf2d8b6fd7b727 authorize this bounded evidence update. That exact revision was the accepted protocol and prepared source for both actions. The experiment safety policy and Windows MSAL protocol govern the observations.

Scope and Non-Goals

Update the existing protocol history/current stopped disposition and its baseline consumer. No probe/source change, capacity increase, new experiment, account or configuration change, product implementation, Profile selection, or support claim.

Record-System Impact

Existing experiment protocol and V1 public-contract baseline only. The protocol owns ordered evidence and limits; the baseline owns the bounded source interpretation and implications. No new record, family, control, schema, or route.

Evidence and Reasoning

• Attempt 10 prepared the exact merged source using retained public packages. Build took 3.32 seconds with zero warnings/errors; the synthetic selector/URL/failure-output self-check passed. Source, artifacts, dependencies, runtime, lock, and launch setup were independently checked before readiness was announced.
• The agent stopped and waited for a new explicit readiness response before attempt 11. Short preflight then verified current authority, host, retained subject, local inputs, and the completed journal.
• Attempt 11 ran 2026-09-11 01:43:12.7868381 to 01:43:33.3991836 UTC, with acquisition-failed and launcher exit 2. One exact match selected the real account. No AuthenticationResult or resource request followed.
• Selected error fields: service-or-broker, unknown_broker_error, Unexpected, broker code 2147786073, service status 0, retryable false, no UI-required classification. The pinned MSAL default mapping supports the category but does not identify the cause, observed HTTP response, or remote account rejection.
• Operator observation: input form, apparent automatic filling/submission, then a brief surface that appeared to be WAM before the windows closed. Exact WAM identity and detailed sign-in/MFA/consent steps were not established.
• One input operation completed normally; probe/input processes exited, hashes still matched, and attempt 12 is absent. This action was not recorded as a timeout or cancellation.
• Preserve cumulative usage: fetch 1/1, prepare 6/6, inspect 1/1, silent 1/2, interactive 3/3, discovery 1/3. The sequence is stopped and conditional remaining slots cannot be used.

Identity and Security Effects

The same nominated personal account, single resource, Microsoft-owned client, common authority, scope, existing Windows session, and broker options were used. Only selected flags, structured errors, and sanitized operator observations are retained. No private identifiers, URLs, token material, broker text, screenshots, or response data. No helper fallback, PAT, account/cache cleanup, shared-broker termination, installation change, object/pack request, or resource write. Failed completion does not imply reversal of provider session effects.

Validation

Accepted Windows preparation/self-check passed; local artifacts and the complete eleven-action journal were checked. Normal hk commit checks and CI are required. This change does not replay an experiment.

Review and Disposition

Independent research-evidence and record-system reviews are required. All seven rechecks are considered: no product interaction/account/cache decision, platform/Profile selection, Wave change, or release occurs. Existing source findings retain their limits; RECHECK-007 prerequisites remain unresolved. No new owner scope or risk decision is proposed.

Upstream Provenance

No source import. The generic broker-category interpretation uses already pinned MSAL 4.83.1 at d5d7de6b103f0d9dd7bca9bf13cbb9f3da37bc9f, WamAdapters.cs lines 116–120.

[hcoona]

Independent reviewer: /root/preparation_review, independent of authorship and implementation.

Reviewed exact tree c5771d0fc00bec210266858dcfc92bbd0069b82a against accepted target facfec1aa86b88601a9a9e7835bf2d8b6fd7b727 under the accepted research-evidence-review and record-system-review Skills.

No material findings.

The reviewer independently matched retained source files, prepared artifacts, lock hash, the eleven-action journal, attempt-11 result, and decimal/hex error-code conversion. Attempt 12 is absent. Preparation 10 retains its earlier independent archive/package/runtime/self-check verification. Pinned MSAL source supports only the generic exception category; no root cause or remote-rejection claim is inferred. Service status zero remains an unobserved HTTP default, and earlier failures/visibility differences remain unresolved.

The operator's brief possible-WAM observation is explicitly uncertain and separate from automated flags; no completed sign-in/MFA/consent is inferred. The explicit readiness handoff preceded this action. The existing protocol and baseline remain the only canonical carriers, updated together, with no new capacity, source change, or support/Profile/architecture claim. The stopped disposition retains fetch 1/1, prepare 6/6, inspect 1/1, silent 1/2, interactive 3/3, discovery 1/3; conditional remaining slots cannot be used.

All seven rechecks were considered. No Wave/release or product/platform/Profile selection occurs; existing bounded conclusions and RECHECK-007 prerequisites remain unresolved where required. Review was read-only and performed no helper/subject/account/resource/UI or private-input action. Normal hk and CI remain separate gates.