context: capabilities.json links 31 module pages that do not exist #592

Activity

1. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Joint decision (orchestrator + advisor), 2026-11-13, on parallelizing the remaining issues. The owner asked in pane t12: "近7个issues，还有多久才能收完？能不能并行".

   1. 0.14.1 (0.14.1: unblock the repo-harness archctx 0.14 pin (#579, #580) #583, release: prepare archctx 0.14.1 #582) is in flight and finishes first. main stays frozen until the release candidate chore(release): prepare archctx 0.14.1 (#582) #591 merges. codegraph-adapter: read the index only through the in-process read-only handle #574 S1 (feat(codegraph-adapter): one in-process read-only read session (#574 S1) #589) merges after 0.14.1 is published.
   2. Started now, in parallel, in files codegraph-adapter: read the index only through the in-process read-only handle #574 does not touch:
      • context: capabilities.json links 31 module pages that do not exist #592, Low. Regenerate .ai/context/capabilities.json from its authority; do not hand-edit the 31 paths. The worker names the generating command. If the generator lives in aimpact-inc/repo-harness, that is a boundary question back to the orchestrator and advisor. Write scope: .ai/context/ only.
      • ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576, High: one GPT review plus one Opus review. One model validator over a set of model files, called by both the YAML store and the ledger read path. It is not a second validator patched up to parity, and there is no compatibility path. Write scope: runtime-daemon index.ts (validateLedgerModelFiles and its caller) and model-store-yaml validateModel.
   3. codegraph-adapter: read the index only through the in-process read-only handle #574 split. Right after S1 merges, a move-only slice S1b (Medium, one GPT review) splits codegraph-adapter/src/index.ts by responsibility: readiness and status, import population, projection handshake, snapshot, CLI provider. Behavior does not change. Then S2+S3, S4 and S5 run in parallel, each in its own module, and S6 comes last.
   4. complete: codegraph sync runs twice per complete #584 and codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585 fold into codegraph-adapter: read the index only through the in-process read-only handle #574 S2+S3.
      • complete: codegraph sync runs twice per complete #584's projection-sync half is S3 code.
      • complete: codegraph sync runs twice per complete #584's half at runtime-daemon/src/index.ts:791 lands only after ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576 merges, because ledger read mode: validateModel has no parity with YAML validation (schemas, topology, state machines) #576 writes that file. One writer per file applies by file, not by region.
      • codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585: measure memory at 64k import nodes. Raise the limit if that is safe. Otherwise keep the deterministic importNodeLimitExceeded and close codegraph-adapter: the 50 000 import-node read limit is reached at about 8x repo-harness #585 with the measurement.

   Seat: orchestrator t7
2. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Claim: writer and head owner is Pi seat t2kh (worker-light), on branch fix/592-capability-links from main 27c68b2. Tier Low. The merge waits for the 0.14.1 freeze to lift.

   Seat: orchestrator t7
3. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Boundary. .ai/context/capabilities.json is written only by repo-harness 0.32.0 (aimpact-inc/repo-harness: scripts/capability-config.ts, src/effects/architecture/capability-resolver.ts, src/core/capabilities/registry.ts). It cannot be driven from this repository to fix the links:

   • add is append-only;
   • sync never touches architecture_module;
   • init writes only when the file is missing.

   Under repo-harness/v1, this repository projects one module page (docs/architecture/modules/architecture/context.md) for 31 registry entries, so no regeneration can produce only links to existing pages. repo-harness run capability-resolver validate already reports the reverse problem here, 'orphan architecture module: docs/architecture/modules/architecture/context.md'.

   Joint decision (orchestrator + advisor): the fix belongs to repo-harness, where the authority for architecture_module lives. The advisor routed it to the repo-harness orchestrator t1fh with this evidence. This issue closes as a boundary, with a link to their issue once it exists. Nothing is hand-edited here.

   Seat: orchestrator t7
4. Ancienttwo commented on Nov 13, 2026

   

   Ancienttwo

   on Nov 13, 2026

   OwnerAuthor

   More actions

   Closed as a boundary. The fix is tracked upstream in aimpact-inc/repo-harness#2707 (under #2624): under an archctx projection, the module page path comes from the projection manifest, or architecture_module is omitted. Nothing is hand-edited here; .ai/context/capabilities.json changes when repo-harness regenerates it.

   Seat: orchestrator t7
5. Ancienttwo

   closed this as not plannedon Nov 13, 2026