Releases: luca-mastrostefano/agent-native-setup
Releases · luca-mastrostefano/agent-native-setup
Release list
v0.6.1
Patch release: a clearer name for the update command, and releases are now version-guarded.
/update→/update-agent-scaffolding(#7) — a precise name for the command that refreshes the agent-native scaffolding. On a project's next update the old/updateis removed and the renamed one created automatically — no action needed.- Release version guard (#8) —
task releasenow checks the bump against the migration registry (reusing the update gate's ownbreaking_series), so a breaking change can't ship with a compatible label. Dev tooling; no effect on generated projects. This release is the first cut through it.
v0.6.0
First release with the update capability — a scaffolded project can now be refreshed to a newer release instead of frozen at the version that generated it.
Breaking (0.x): the contract is now split. AGENTS.md becomes a thin project map and the standard engineering principles move into a managed INSTRUCTION.md. Projects scaffolded before 0.6.0: run agent-native-setup update (or /update) — it's gated, walks you through the split, and is non-destructive (it never overwrites your edits).
What's new
agent-native-setup update— regenerate + classify: refresh pristine managed files, never touch seed (user-owned) files, report your edits as conflicts to reconcile, remove pristine orphans.--dry-runpreviews; git is the review surface and undo.- Version-driven gate — semver as a difficulty contract. Compatible updates (same breaking series) are autopilot; crossing a boundary is gated (
--yes) with an ordered migration-step runbook inUPDATING.md. - Discovery —
update --checkstaleness nudge wired into the generated SessionStart hook, and a/updateskill. AGENTS.md→ managedINSTRUCTION.mdsplit — the first agent-assisted migration; standard-contract improvements now propagate on update.
Implements RFCs 2026-06-20 (engine) and 2026-06-22 (version model). Changes: #4, #5, #6.