adopt-claudinite

Open an adoption issue first, then fetch the canon and run the bootstrap script's fast path, which is idempotent. Answer every pending interview question in batched AskUserQuestion passes, create the executor routine, and land the adoption as one commit referencing the issue.

Trigger the repo's own update flow by dispatching the claudinite-scheduler.yml workflow with wake=update via GitHub MCP tools, using the default branch as ref. Never run apply-vendor-set.mjs against a stamped repo, since it skips migration records permanently.

A fresh project's interview takes two passes because declaring the project-class pack pulls in a requires closure whose questions cannot exist until the pack is declared. It never takes more, since answers are stored verbatim and need no clarifying follow-ups.

No. apply-vendor-set.mjs is only correct at bootstrap when the repo is at version zero. On a stamped repo it advances version stamps without applying intermediate migration records, leaving the repo claiming a version whose shape it was never migrated into.

A stored answer whose question the pack no longer declares is surfaced as an advisory finding by the skill's hygiene check. It is never run-failing, so a canon-side question rename cannot break CI, but the stale intent should be removed or re-keyed.