ar-agents-remember

After the MCP installs the runtime and skills (scaffolding), take over the rest of setup: install a start-of-session/chat hook (or place the coordinator directive in the harness's always-on instructions), set up the memory repo (ask scaffold vs existing), bootstrap onboarding when scaffolding new, and configure providers to index the code and memory.

Initialize or repair the Agents Remember memory root for a target repository. Defaults to repo-local internal memory; creates an external memory repo only when the developer explicitly asks for external memory.

Capture confirmed findings, route them to the right durable task-local path, and propagate factual current-state clarifications into onboarding immediately when allowed.

Bootstrap onboarding for undocumented repos or existing memory slices. Builds root overviews, route-local overview pillars, evidence packs, file cards, onboarding waves, deleted-slice cleanup, curator reviews, and handoff while keeping the orchestrator thin.

Choose retrieval strategies across memory substrates: semantics for known concepts with unknown structure, relationships for known anchors with unknown connections, and intent for hidden contracts and code truths.

Create and maintain file-level onboarding and repo entity catalogs. Enforces strict 1-to-1 source mapping, governing overview links, metadata, and references, and routes package/module/source-slice create, refresh, move, or delete cases to the c-03-repo-bootstrap skill.

Resolve the active Agents Remember context for a target repository, including topology, coordination root, memory root, settings, storage, pathRules, worktree contract facts, ledger path, and branch-gated cross-repo allowances.

Create, attach to, report on, integrate, and clean up Agents Remember worktree-backed tasks while preserving human approval gates and external-memory compatibility.

Carry richer onboarding memory from a source branch into official memory only when the corresponding code has landed on the official branch.

Close out approved Agents Remember edits by preserving explicit commit approval, missing-onboarding checks, external-memory onboarding refresh, memory quality, ledger alignment, and no automatic push for both direct checkout and worktree-backed tasks.

The session job lifecycle the coordinator routes every session into: request -> context/trust checkpoint -> developer-agreed reframe -> deeper research -> decide build mode -> build -> close. Owns research-only exits, the build-mode decision (chat build vs durable w-02-light-task-workflow task), and the job lens (bug/feature/triage/research). Supersedes the retired chat workflow by migrating and modernizing its doctrine.

In-between task workflow for work that needs a durable task file, distinct implementation examples, and an approval gate but still fits a single-page implementation plan as a rule of thumb.