Skip to content

W.0: document why W1/W4/W5/W6 stay as-is (docs; on #37) - #38

Open
cunninghamcard-bit wants to merge 6 commits into
exp/e6-enum-family-auditfrom
exp/w0-wire-docs
Open

cunninghamcard-bit wants to merge 6 commits into
exp/e6-enum-family-auditfrom
exp/w0-wire-docs

Conversation

@cunninghamcard-bit

Copy link
Copy Markdown
Owner

Unit W.0 (PHASES 1W, A9). Docs only. Stacked on #37 (exp/e6-enum-family-audit @ ba36929); the PR base is that branch.

  • Copies A9-wire-transport-and-aisdk-alignment.md from the plan into docs/amendments/ verbatim.
  • Appends a W.0 section explaining why W1 (Fetch boundary), W4 (auth in Fetch decorators), W5 (SSE stays out of Fetch) and W6 (presets are already data) stay as they are. Each item gets its file:line at ba36929 and the ALIGN rule it already meets.
  • Notes that A9's original description of W4 (Azure writing the token at construction) was wrong: BearerTokenFetch resolves the token at request time.

No code changes, so no tests were re-run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant