docs(auth): align 04B custody scope

[Abiorh001]

Intent

Correct WS-XINT-002-04B scope so its runtime can activate guide binding/read without violating deterministic custody parity or weakening transaction-bound PREP.

Design

• allow the canonical AUTH activation-custody ledger for the two existing guide rows
• allow the narrow ART guide-read seam correction: the request carries idempotency plus IDs, never a prepared handle
• require the materializer to lock canonical facts and prepare/consume fresh reader authority on its internally owned same session/root transaction before provider I/O
• allow the architecture parity test and operations status documentation required by those changes

Scope control

No new actions, permissions, migrations, routes, Celery payload/orchestration, upload/storage/parser behavior, submission/review behavior, generic download authority, or ART-03C cutover.

Product behavior

No live route is activated by this planning PR. It only makes the later 04B implementation boundary executable and internally consistent.

Evidence and acceptance proof

• architecture plan re-review: PASS
• security plan re-review: PASS
• QA plan re-review: PASS after adding architecture-test coverage
• final architecture scope re-review for operations doc: PASS
• Markdown links: PASS
• git diff --check: PASS
• hosted Agent Gates/Backend/CodeRabbit rerun on exact amended head

Test delta

No test code changes in this PR. It explicitly permits the implementation to update the existing architecture/custody tests that otherwise reject the approved request-shape and owner changes.

Risks

The main risk is scope expansion. Mitigation: every added file is named, the materializer correction is the sole ART behavior change, and ART-03C/Celery/routes remain excluded.

Human review focus

Confirm the external-handle seam is impossible under session-bound PREP and that same-session preparation/consumption is the correct fail-closed correction.

Merge ownership

Human merge only; this PR does not authorize or perform merge.

[coderabbitai]

📝 Walkthrough

Walkthrough

The 04B guide now permits updates to the AUTH activation-custody ledger and requires atomic updates to its two action rows with catalogue ownership and availability.

Changes

AUTH 04B ledger contract

Layer / File(s)	Summary
Ledger scope and atomic update rules .agent-loop/initiatives/WS-XINT-002-art-auth-end-to-end/chunks/WS-XINT-002-04B-guide-read-binding-activation.md	The allowed implementation files now include the AUTH activation-custody ledger. The guide requires atomic updates to the ledger’s two existing action rows alongside catalogue ownership and availability.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• Flow-Research/workstream#158: Introduces related AUTH activation-custody ledger requirements.
• Flow-Research/workstream#213: Adds the 04B guide whose contract this change updates.
• Flow-Research/workstream#243: Hardens the same 04B guide-binding activation contract.

Suggested reviewers: abiorh-claw

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the documentation change that aligns WS-XINT-002-04B authentication custody scope.
Description check	✅ Passed	The description explains intent, design, scope limits, evidence, risks, and review focus, but it omits several template sections.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ws-xint-002-04b-custody-scope

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}