agent-canon-update

name	agent-canon-update
description	Use when updating AgentCanon itself, refreshing a vendored vendor/agent-canon submodule pin, repairing AgentCanon root runtime views, applying AgentCanon update TODOs, or routing local AgentCanon source commits through a proper AgentCanon branch and PR before parent pin updates.

AgentCanon Update

Reader Map

• Purpose: runtime skill for AgentCanon source updates, parent submodule pin refreshes, root-view repair, and latest-state checklist work.
• Use When: updating vendor/agent-canon/, applying AgentCanon update TODOs, or routing local AgentCanon commits through source PRs before parent pins.
• Tool Commands: run this skill's command packet, then read the canonical update-route and parent latest-state documents.
• Boundary: do not hide dirty AgentCanon source work inside a parent pin update or create branches without the documented reason.

Tool Commands

Use the command packet before applying this skill's workflow:

python3 tools/agent_tools/skill_tool_commands.py show --skill agent-canon-update --format text

Execute the required and task-matching conditional commands that the packet prints.

1. Read agents/skills/agent-canon-update.md.
2. Read documents/agent-canon-update-route.md and documents/agent-canon-parent-repo-latest-checklist.md.
3. Classify the repo as standalone AgentCanon, parent submodule repo, or legacy compatibility repo before running update commands.
4. In parent repos, classify dirty state by AgentCanon update surface: vendor/agent-canon/, parent gitlink, .gitmodules, and AgentCanon-owned root views. Do not let unrelated parent dirty files block the update route.
5. Prefer the high-level parent route:

make agent-canon-update-plan
make agent-canon-ensure-latest

1. If vendor/agent-canon/ contains local AgentCanon source commits or source dirty state, do not hide them in a parent pin update. Route them through an AgentCanon branch/PR first:

bash tools/update_agent_canon.sh merge-main-into-current
git -C vendor/agent-canon push origin HEAD

Reuse the current AgentCanon source branch / PR when it already owns the shared-canon work. Do not create a fresh branch for a bounded follow-up, mid-task user instruction, dirty-state avoidance, or checklist addendum. Record a reason before creating any new branch.

1. After a safe update or PR merge, repair and verify root views:

bash tools/sync_agent_canon.sh link-root
bash tools/sync_agent_canon.sh check

Treat this as the mandatory agentcanon_structure_followup gate whenever AgentCanon source, the parent submodule pin, .gitmodules, root runtime views, shared root-copy surfaces, or parent root sync state changed. Record agentcanon_structure_followup=required before the commands and agentcanon_structure_followup=pass only after the sync check passes. Template / derived parent roots must run this gate from the parent root after AgentCanon source changes are integrated, or while preparing the parent pin/root-view PR.

1. Check and apply parent update TODOs before unrelated work:

python3 tools/agent_tools/agent_canon_update_todos.py status
python3 tools/agent_tools/agent_canon_update_todos.py plan --write

1. Use $agent-update-branch only for parent-repo canon-pin update branches. AgentCanon source edits use a standalone AgentCanon branch and PR. Reuse the current parent branch if it already owns the same pin/update lane.
2. Close out with update route, dirty-surface classification, submodule pin or AgentCanon commit, PR URL if any, root-view check, TODO status, and selected validation evidence.