feat: provenance-drift check + re-pin for project→assistant refer-back#44
Merged
Conversation
A science project resolves the assistant clone at run time (env var → sibling → clone-on-demand) but pins assistant_ref at creation; nothing compared the two. The locate rule now specifies the non-blocking drift check — warn once per session with both commits, offer a re-pin recorded as one journal line, never force a checkout (the per-run manifest stays the record of what was actually used) — and the generated thin AGENTS.md instructs a copilot inside the project to perform it. Completes #43; the resolution order, env var and assistant_ref pin were already locked in this skill. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Completes #43 — the last missing mechanic of the science-project → assistant refer-back model locked in
skills/start-new-project.md. A project resolves the assistant clone at run time ($AUTOLENS_ASSISTANT→ sibling → clone-on-demand) but pinsassistant_refat creation; nothing compared the two. This adds the non-blocking provenance-drift check: after resolution, compare the clone's commit toproject.yaml'sassistant_ref.commit; on mismatch, warn once per session (both commits + what drift means), offer a re-pin recorded as one line in the day'swiki/project/journal entry, and never hard-block or check out the pinned commit — the per-run manifest'sassistant.commitremains the record of what was actually used. The generated thinAGENTS.mdtemplate carries a one-line mirror so a copilot invoked inside a project performs the check without reading this skill first.Start_dev audit note: the prompt's other three bullets (resolution order,
AUTOLENS_ASSISTANTenv var,assistant_refpin + manifest provenance) were already shipped in this skill onmain— this PR implements only the genuinely missing fourth.API Changes
None — markdown-only change to one skill (the locked design doc + its generated templates). No Python surface.
Test Plan
pytest autoassistant/tests -q— 39 passedautoassistant/audit_skill_apis.py— 57 files, 117 symbols, 0 missing/broken--check-citations— 90 files, 388 citations, 0 missing pathsassistant_ref.commit/ manifestassistant.commitkey names match the templates in the same fileValidation checklist (--auto run — plan was not pre-approved)
heart-ack:block)🤖 Generated with Claude Code