refresh

Refresh

You receive a task: bring the contextualizer's existing references into agreement with the current upstream state of every registered source. The named checks in verify.sh (plus the permalink-density lint for SHA-pinning) validate your output; the four reference invariants are your authoring targets — not all are machine-checked (see § Output contract). How you reason about drift is your call — there is no Stage -1/1/2/3 prescription, no fixed keystroke menu, no required worker dispatch.

Contextualizer root

Engine workflows operate inside a contextualizer installed as a project skill at one of three install levels:

• User-level: ~/.claude/skills/<slug>-context/
• Local-user-level: ~/.claude/local/skills/<slug>-context/ (when in use)
• Project-level: <repo>/**/.claude/skills/<slug>-context/

Every path below — research/..., references/..., verify.sh — resolves relative to whichever directory matches. Before reading or writing anything, locate the root by searching all three install levels in order:

Run the script in shared/locator-block.md verbatim before proceeding.

CTX_PROPOSED="${CTX_ROOT}.proposed"

/skill-engine:refresh <name> names the contextualizer to refresh — the directory name without the -context suffix; with no argument, auto-detection applies. The staging-directory model (how $CTX_PROPOSED mirrors the live tree and the sandbox-block diagnostic) is in references/tool-and-output-mechanics.md. Read it before your first write of a run.

Output contract

Two things, both load-bearing:

1. Updated reference files in references/ (where applicable), each still citing its source by path plus content-hash (see 02-artifact-contract.md). Each still satisfies the four reference invariants (definitions owned by 02-artifact-contract.md §Navigator size budget and §Long references — do not restate them elsewhere):
   • first-5K — the navigator's standing instructions (invariants, critical rules, dispatch logic) fit in the first 5K bytes of SKILL.md body; the catalog table is a TOC and is exempt.
   • depth-1 — no more than one level of pointer indirection.
   • max-100-line-TOC — any reference body over 100 lines carries a TOC marker within its first 30 lines.
   • SHA-pin — every citation pins to a specific SHA, not a moving branch or tag.
2. Updates to research/source-paths.json reflecting upstream transitions you detected (lifecycle.state for each source; proposed_url on moved; last_checked and last_checked_sha timestamps). The four-state field on source-paths.json is the single source of truth for upstream state.