2 Commits

Include renames

Author	SHA1	Message	Date
Omar SobhandClaude Opus 5	fe2451fd60	feat(workforce): missions hire the agents you already have, and name them by role ... Every zeroclaw mission minted a fresh team of claws. They are created `lifecycle = 'permanent'` and nothing reaps them until the MISSION is deleted, so the roster grew by a whole team per mission while each member worked exactly once — "My Workforce" was a list of strangers, and upskilling had nothing durable to act on. A mission now hires the claw that already does the job, matched on `agent_template_link (template_id, role_slot)`, minting only what is missing. Oldest first, so reuse concentrates on the same few claws and their brains actually accumulate rather than spreading thinly across a growing pool. A claw on a RUNNING mission is not offered. Two missions driving the same ZeroClaw agent and the same `.brain` at once is a data race with a model on the other end of it, and minting a second claw is much cheaper than reasoning about that. A reused claw is NOT re-seeded from the template's brain_seed — that would overwrite what it learned with its starting point, which is precisely the accumulation this exists for. Names are the role now (`planner`), not `"{mission} · {purpose} · {template} · {slot}"`. That produced "verify: a repo-less research mission keeps its output · mission · Rust SDLC · planner" — unreadable in the roster, the API and every log line at once. Which mission a claw is on is context a caller can join to; it is not its name. And the half that makes reuse safe rather than destructive: deleting a mission now purges only claws no OTHER mission still employs. Without it, tidying up one mission deletes staff another one holds — presenting as the roster quietly shrinking rather than as an error. A test asserts the guard exists inside the reaper AND runs before the purge, because a check after it is decoration. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-08-10 07:18:12 -07:00
Omar SobhandClaude Opus 4.7	85a97dffca	slice 3.5d: agent_template_link + brain seed helper + skills merge ... Ships the lineage layer that ties agents back to their team template and wires the MCP skills server to actually merge template default skills with per-agent overrides. Migration 0050 adds `agent_template_link` (agent_id PK, template_id, template_version, role_slot, seeded_at, created_at + indexes for template/role lookups). Populated at agent-materialization time by Slice 4's mission-launch orchestrator; read here by the skills MCP server and by future level-up (Slice 8.5). New Rust surface: - cm_db::repo::agent_template_link (upsert / get / mark_seeded / agents_for_template — the last is what level-up's "prompt upgrade on template N+1" query needs) - cm_api::brain_seed::ingest(claw_id, seed_md, identity_prompt) opens cm_brain::ClawBrain on spawn_blocking, sets system_prompt on first touch, writes seed as agent_md, commits. Idempotent — skips when agent_md already populated. - cm_api::mcp_skills::mcp_skills tools/call now resolves the caller agent's template + role via agent_template_link and merges template default skills with per-agent overrides (was overrides- only in Slice 3.5b). - cm_api::team_template_loader now binds template_role_skills after upserting each template — looks up each declared skill by name, attaches with pin_in_context=true for foundation skills and the first two role skills. Missing skills log + skip. - Boot ordering: skills load BEFORE team templates so the binding lookup resolves. Follow-up (Slice 4): mission-launch orchestrator calls brain_seed::ingest + agent_template_link::upsert when minting a team from a template. Until that lands, the link is populated only by manual writes; the MCP merge is silent-no-op for agents without a link (falls through to overrides-only), which matches the pre-3.5d behavior. Co-Authored-By: Claude Opus 4.7 <[email protected]>	2026-07-19 14:16:16 -07:00