Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/hygiene-history/ticks/2026/05/01/0947Z.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
| 2026-05-01T09:47:00Z | opus-4-7 / autonomous-loop tick | 98fc7424 | PR #967 thread-drain — 6 threads on the peer-call README + B-0119/B-0120 cross-refs PR resolved this tick. Two classes of fix: (1) **Persona names in current-state doc (P1, line 247+253 of README, real fix)** — `tools/peer-call/README.md` had "Otto + Kenji" as table-cell description and prose mention of "Otto + Kenji additions"; per `.github/copilot-instructions.md:306-362`, current-state surfaces (code/docs/skills) outside the closed-list history surfaces require role-refs not persona names. Reworded both occurrences to "the Anthropic-side Claude-code-instance personas" / "the Anthropic-side (Claude-code-instance) peer additions". B-0121 filename slug `otto-kenji-*` stays as direct-link because backlog rows are closed-list history surfaces (persona-name carve-out applies). (2) **B-0122 forward-references (P1+P2, 4 of 6 threads)** — B-0122 row is filed in in-flight PR #966; not yet on main. Updated B-0119 + B-0120 YAML composes_with lists with inline `# B-0122 ... is filed in the in-flight PR #966` comments. Updated README's table row for B-0122 to explicit "filed in in-flight PR #966; link will resolve once that PR lands" callout. **Ninth canonical application of forward-reference fix-shape this session**. All 6 threads resolved via GraphQL. Cron 98fc7424 healthy. | [PR #967: 1 commit (45f350e) addressing 2 real findings (persona-name role-refs) + 4 forward-references + 6 thread-resolutions] | The persona-name-in-current-state-doc finding is a class worth naming explicitly: **persona-name role-ref discipline (P1, real fix)**. The carve-out hierarchy: closed-list history surfaces (memory/, docs/ROUND-HISTORY.md, docs/DECISIONS/, docs/research/, docs/hygiene-history/, commit messages, backlog rows) ARE allowed persona names; current-state surfaces (code, docs except those listed, skills, behavioral docs, public prose) MUST use role-refs. The README is current-state; B-0121 backlog row's filename slug is closed-list history. Same file (this PR) demonstrates both: README cells get role-refs, the backlog filename stays as `otto-kenji-*`. Future-Otto: when authoring a current-state doc that needs to reference work-in-flight that has persona-name slugs, use the link-display-text-as-role-ref pattern: `[B-0121](otto-kenji-...)` reads visually as "B-0121" while preserving the slug as historical artifact. |
Loading