Trace authority and evidence

Produce an authority map without changing behavior.

1. Read AGENTS.md and spec/README.md completely.
2. Search existing entity IDs, aliases, criteria, anchors, relations, revisions, sources, and lifecycle.
3. Follow the coherent chain from knowledge or decision through semantic owner, host boundary, Adapter profile, tests, implementation, exports, and documentation where applicable.
4. Use internal/contracts/** only for explanation or an uncataloged gap. Use dated records as context, never as project authority.
5. Distinguish governed fact, implementation evidence, public projection, observation, proposal, and unknown.
6. Treat implementation disagreement as drift to investigate, not an implicit spec amendment.
7. Record negative boundaries, direct and indirect consumers, generated projections, validation commands, and unresolved conflicts.

Return paths and entity anchors precise enough for another skill to act without repeating discovery. Stop at a contradiction that requires semantic choice.

Explicit handoff

Do not load or execute another skill. Return exactly one handoff conforming to internal/agent-operations/schemas/skill-handoff.schema.json. Carry required prior artifacts by reference, include every artifact this leaf produces according to skills.yaml, and set nextSkillId to one eligible registered leaf or null.

Communicate with the user in the user's current language. Keep repository identifiers canonical.