[qiansc]

Summary

Moving a repository registration with context source add repo --ref <sha> only changes the registration. Until now, nothing processed the new commit. The next production or verify reported every cited region whose text moved or changed, so a routine re-pin produced dozens of warnings and no direct way to settle them. This PR makes the update a single, routed step:

• context update --pending finds registered repositories whose commit moved past the processed version recorded for approved knowledge. It needs no input file.
  • It prepares the usual source update. Only pages whose cited text changed are candidates, listed in the new changed_references (changed or unavailable). The list can be empty.
  • The scope decision (scope_summary, new_topics) is still required, so additions and shared dependencies are reviewed before the baseline advances. Moved citations update their locations when the update settles.
• Workflow route. A new process-source-update node (sources.update_pending, reason route.source.update-pending) runs the command before the idle reopen-cleared-task gate. The procedure is a recommended read, not a required one.
• CLI guidance. source add repo returns a next hint when the moved commit leaves processed knowledge behind. verify warnings name context update --pending when a cited repository moved.
• Shallow and partial checkouts. Settled-commit history reads share one reader per inspection, check each commit once, fetch a missing commit once (--depth=1) and read one file at a time per checkout. Recovered checkouts no longer misreport moved citations as changed. Large updates no longer trip remote rate limits.

Local verification

• Community portal (Context 3b0ce0a/dabfa49 → ef395ea): verify reported 35 issues before. update --pending asked about 8 pages (19 citations); the moved citations elsewhere relocated at settlement. After review and build, verify reports 0 issues with both this build and the released 0.7.87.
• Internal workspace (TTKB 119645f → 3d6eb3d): there were 60 warnings before. update --pending now finishes in under a minute, with 21 candidate pages and 52 genuinely changed citations. The earlier attempt reported 64 unavailable because of rate limiting and a processed commit missing from the remote. The content revisions are not part of this PR.

Tests

• New projectPendingSourceUpdate.test.ts:
  • only moved citations plus a new export still require the scope decision, and the baseline holds until it is submitted;
  • candidates are limited to changed citations;
  • concurrent history reads in a shallow checkout share one fetch and confirm every moved citation (this test fails on the previous reader handling);
  • a missing commit is fetched into a shallow checkout.
• Workflow fixture source-update-pending.yaml; existing fixtures carry update_pending: false.
• Related tests pass locally (pending update, settled-reference relocation, knowledge update: 27 tests); typecheck and lint are clean. The full suite runs in CI.

🤖 Generated with Claude Code