v1.4.0

Added

• Migrations are forward-only — a new immutability rule. A migration becomes immutable the moment it is either committed to git or deployed to any environment: editing a committed migration is forbidden (fix forward with a new db migrate), and an uncommitted migration may be edited/regenerated only after confirming with the user that it has not reached production (a prod deploy from a dirty tree can push one). Added at the decision layer in agents/builder.md and as an authoritative section in skills/cli/references/migration_system.md; the "Fix a broken migration" / "Remove a migration" troubleshooting steps and the cli skill's manual-fix list were reconciled to gate on uncommitted-and-not-deployed instead of telling the agent to edit migration files.
• AGENTLINK_VERSION stamp in agents/builder.md. Records the current version (plugin + CLI ship in lockstep, same number) and how the agent should reason about contract drift from a project's agentlink.json (version / appliedVersion). Kept in sync by the release script.

Changed

• Prefer the project-local CLI (pnpm exec agentlink) over npx …@latest for in-project work (pairs with the CLI's 1.4 devDependency pinning). agents/builder.md and the cli skill gained a "Running the CLI" section explaining the convention and the name split — the package is agentlink-sh, the installed binary is agentlink, and bare npx agentlink is unsafe (it resolves a different npm package when no local install exists). Swept ~230 in-project command references across the skills, README.md, rules/agentlink.mdc, and the destructive-DB hooks from npx agentlink-sh@latest <cmd> to pnpm exec agentlink <cmd>; create and recovery commands keep @latest (no local CLI exists yet). The hooks now point users at pnpm exec agentlink db rebuild — the block matcher is invocation-prefix-agnostic, so destructive-reset blocking still fires.