Skip to content

feat: provenance-drift check + re-pin for project→assistant refer-back#44

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/assistant-ref-mechanics
Jul 10, 2026
Merged

feat: provenance-drift check + re-pin for project→assistant refer-back#44
Jammy2211 merged 1 commit into
mainfrom
feature/assistant-ref-mechanics

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

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 pins assistant_ref at creation; nothing compared the two. This adds the non-blocking provenance-drift check: after resolution, compare the clone's commit to project.yaml's assistant_ref.commit; on mismatch, warn once per session (both commits + what drift means), offer a re-pin recorded as one line in the day's wiki/project/ journal entry, and never hard-block or check out the pinned commit — the per-run manifest's assistant.commit remains the record of what was actually used. The generated thin AGENTS.md template 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_ASSISTANT env var, assistant_ref pin + manifest provenance) were already shipped in this skill on main — 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 passed
  • autoassistant/audit_skill_apis.py — 57 files, 117 symbols, 0 missing/broken
  • --check-citations — 90 files, 388 citations, 0 missing paths
  • Consistency pass: section cross-references resolve; assistant_ref.commit / manifest assistant.commit key names match the templates in the same file

Validation checklist (--auto run — plan was not pre-approved)

  • Effective level: safe (header: safe, cap: feature/small → safe)
  • Plan: on the issue (feat: project provenance-drift warning + re-pin for assistant refer-back #43), written at start, unmodified since
  • Gate: tests 39 pass + symbol/citation audits clean · smoke n/a (markdown-only skill edit, no downstream script surface) · review CLEAN (review-faculty surface: 1 commit, 1 file, +14; consistency + citation checks in lieu of runtime verify for a doctrine diff) · Heart YELLOW within launch ack (6 reasons, exact set recorded in the task's active.md heart-ack: block)
  • Human: plan sound in hindsight?
  • Human: diff matches plan (no scope creep)?
  • Human: merge, amend, or reject — then log the outcome

🤖 Generated with Claude Code

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>
@Jammy2211 Jammy2211 merged commit 56bd9c2 into main Jul 10, 2026
1 check failed
@Jammy2211 Jammy2211 deleted the feature/assistant-ref-mechanics branch July 10, 2026 07:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant