docs: accept leader summary notification architecture

.project-docs/05-agent-entry/integration-gate.md

@@ -6,6 +6,7 @@ Use this gate to promote completed task facts into canonical project memory.
 
 - Run in an exclusively owned integration worktree.
 - Hold the repository integration lock.
+- For a single completed Feature, create the Integration worktree from that Feature commit so its task-owned records are already inside the Integration task's recorded base. Verify the target default branch is an ancestor or reconcile it explicitly before canonical edits; starting from the older default branch and then introducing another task's record will correctly fail the drift gate.
 - Verify the task commits being integrated are present.
 - Review source task records, task-prefixed supporting records, promotion candidates, and semantic conflicts in read-only mode.
 - Write integration notes only to the integration task's own task record or `{task_id}__<slug>.md` supporting records.

.project-docs/05-agent-entry/read-before-planning.md

@@ -3,11 +3,11 @@
 Before writing any coding plan, follow this order:
 
 1. Run the Concurrent Task Gate.
-2. Read memory-index.md.
+2. Read `.project-docs/05-agent-entry/memory-index.md`.
 3. Read the active task record at `.project-docs/30-worklog/tasks/{task_id}.md`.
-4. Read project-positioning.md.
-5. Read current-state.md as the integrated snapshot.
-6. Read decision-index.md and system-overview.md.
+4. Read `.project-docs/00-brief/project-positioning.md`.
+5. Read `.project-docs/30-worklog/current-state.md` as the integrated snapshot.
+6. Read `.project-docs/10-decisions/decision-index.md` and `.project-docs/20-architecture/system-overview.md`.
 7. Inspect other locally active task scopes.
 
 Then read additional files when relevant: