docs(federation): record M3-07/09 merges + fix M3-11 dependency DAG #678
Reference in New Issue
Block a user
Delete Branch "chore/fed-m3-dag-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
FED-M3-11depends_on:M3-02, M3-09→M3-02, M3-04, M3-05, M3-06, M3-09.Why
The original M3-11 edge set captured the harness (M3-02) and client (M3-09) but omitted the server verbs (M3-05/06) and scope service (M3-04). The E2E acceptance cases #1–#5/#8–#10 exercise list/get over mTLS, so those are hard prerequisites. The under-specified DAG caused a premature M3-11 dispatch this session (caught at intake by coder1). Also records the M3 read-path invariant scope so it isn't mis-asserted: no-persist + existing enrollment audit only; read-verb audit-log writes are deferred to M4.
Risk
Docs-only; no code paths touched.
🤖 Generated with Claude Code