Repository navigation
docs(id): Phase 13 plan/issues cite pre-split line numbers; F11.12 status inconsistent across plans #841
Description
Some references in the Phase 13 plan and its issues point at code that moved in the F11.10 split:
- The plan and id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 cite
world_caps.rs:55forCATALOG. Line 55 isMAX_WANTS_BYTES;CATALOGis around:71-89. - The plan cites
world_session.rs:107/:264forClientFrame/ServerFrame. They are now inpkgs/id/src/world_session/types.rs:76/:233. - id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 cites
pkgs/id/src/world.rs. Capability execution is now inpkgs/id/src/world/actor.rs.
F11.12's status also disagrees between documents. The Phase 12 plan's sequencing lists it with done Phase 11 work, but .opencode/plans/2026-10-20_phase-11-status.md says Planned. The status tracker is right: there is no id world journal check/backup yet (see the comment on #227). F11.12 gates every new Phase 13 frame kind, so the inconsistency matters.
Fix: update the references to symbol names, which survive moves better than line numbers, and reconcile F11.12's status.
Acceptance criteria
- The Phase 13 plan and issue id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 cite
CATALOGby symbol name (inworld_caps.rs) instead of the staleworld_caps.rs:55line number. - Plan references to
ClientFrame/ServerFramepoint atpkgs/id/src/world_session/types.rsby symbol name, and id: Phase 13 F13.7 client-side capability providers under the ceiling model #789's capability-execution reference points atpkgs/id/src/world/actor.rs. - F11.12's status reads the same in the Phase 12 plan sequencing and
.opencode/plans/2026-10-20_phase-11-status.md— Planned, matching the status tracker (noid world journal check/backupexists yet, per the Define rollback compatibility for world profile journal entries #227 comment). - No remaining Phase 13 plan/issue reference relies on a bare line number for code that moved in the F11.10 split.
Activity
dezren39 commentedon Oct 26, 2026
Intake review
Still live (verified this run): no merged PR since updates the Phase 13 plan references or reconciles F11.12's status, and the staleness mechanism (bare line numbers into code that moved in the F11.10 split) is exactly the kind that recurs if fixed with new line numbers. Not closed. Acceptance criteria appended to the body this pass.
Related: #789 (cites the stale
world_caps.rs:55andpkgs/id/src/world.rsreferences) and #227 (the F11.12 comment — noid world journal check/backupexists yet, which is why the status tracker is right and the Phase 12 sequencing is wrong).Notes / risks: priority/normal, effort/s — small docs diff, but F11.12 gates every new Phase 13 frame kind, so the status half matters more than the citation half. Fix by symbol name, not by updated line number, or this issue re-files itself at the next split.
Suggested approach: one docs PR touching the Phase 13 plan, the Phase 12 plan sequencing, and #789's references:
CATALOGinworld_caps.rs,ClientFrame/ServerFrameinpkgs/id/src/world_session/types.rs, capability execution inpkgs/id/src/world/actor.rs, F11.12 = Planned everywhere.🤖 Fleet monitor intake enrichment — labels normalized, acceptance criteria appended, and
meta/enrichedapplied this pass.dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 1, 2026
🤖 Agent note · triage verdict: citations stale; status needs updated assessment
b56ccda5c4904abbf24639871e9a829bb391f4ea, the Phase 13 plan lines 34, 50 and 59 still use pre-split paths/line references, and id: Phase 13 F13.7 client-side capability providers under the ceiling model #789 retains old references; current symbols areClientFrameandServerFrameinworld_session/types.rsandCATALOGinworld_caps.rs.ExecutionProfile; the original issue assertion that this remains wholly planned is stale. F11.12 also includes journal check/backup CLI; establish present status separately rather than simply mark the whole feature done or planned. Preserve dated snapshots as historical and distinguish journal compatibility from all transport frames.1 remaining item
dezren39 commentedon Nov 1, 2026
🤖 Agent note · triage done and follow-up queued
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
world/actor.rs), and reconcile F11.12's status to Planned in the Phase 12 plan sequencing.Merge pull request #3778 from developing-today/queue/4861-841-phase-refs
dezren39 commentedon Nov 1, 2026
🤖 Agent note · done
ClientFrame/ServerFrameandCATALOGby symbol in their current files; Phase 12 sequencing now lists F11.12 as still planned with the reason recorded, matching the Phase 11 status tracker; issue id: Phase 13 F13.7 client-side capability providers under the ceiling model #789's status line now points atpkgs/id/src/world/actor.rsand theCATALOGconstant. All references verified against main b4c4a99 (CATALOG atworld_caps.rspub const CATALOG; frame enums inworld_session/types.rs; noid world journal check/backupsubcommand exists — onlydoctor --journal).