v2.8.0: D1 migration autonomy, model-tier seats, installer --check

Added

• D1 migrations that are additive and reversible now run start-to-finish in one task instead of pausing to ask (stack.C8); the ask-first gate stays only for the genuinely irreversible case.
• install.py --check prints installed vs latest version and exits, and the install prompt is skipped when you install from the exact checkout you're on.
• New lookups: macOS code-signing/TCC, and which coding agents read AGENTS.md.
• Every multi-step task re-reads the original request at the finish line and reports any missed demand instead of quietly dropping it (agent.B2).
• Anti-bias intensity pack and skill-token dispatch rule for the Gemini/Antigravity bootstrap.

Changed

• A release now syncs every record surface — plans, arch/feat docs, README, task notes, bound standards docs — not just docs under docs/.
• Research docs are frozen event records with dated amendments; a successor doc is required only when the decision itself changes.
• Council seats are declared by tier (top/mid/cheap), not by a Claude model name, so other hosts use their own cheaper models.

Fixed

• The update-check hook never detected updates (both changelogs start with Unreleased); it now compares the first real version.
• releases.json now has a real "internal" type instead of disguising internal-only releases.
• Windows installer printed a broken bash propagate command; both blocks now print the correct per-platform command.

Full Changelog: 2.7.0...2.8.0

v2.7.0: agy skill-token dispatch, closure re-anchor, anti-bias pack

Added

• Closure re-anchor in the always-loaded core: before reporting a multi-step task done, re-read the original request and check off every explicit demand instead of trusting memory.
• New GEMINI.md rule 14: a /skill token must be dispatched before any other action, even mid-sentence, so agy can no longer skip a named skill and start solo work.
• Owner-ordered anti-bias pack for agy: stronger stop-and-listen enforcement during communication, plus a direct "no filler" communication rule.

Fixed

• Deployed GEMINI.md had two duplicate section headings; renumbered.
• A stale rule count in the internal agy-worker reference doc.

Full Changelog: 2.6.1...2.7.0

v2.6.1: release.B1 web-drift threshold, akiship B8 phrase-list SSOT

Fixed

• release.B1 Drifted threshold is now explicit per app type — web apps drift at one unshipped version, not two. A web app's Pre-bump/Mid-release conclusion is now confirmed against the production baseline instead of local files agreeing with each other, and recovery always squashes backward — never legitimizes an orphan forward as a tag/Release.
• Completion-intensity phrase list and B8 escalation floor consolidated to one canonical site (release.B8) — six near-verbatim copies across skills/akiship/SKILL.md, payload/index.md, and README.md trimmed to pointers.

Full diff: 2.6.0...2.6.1

v2.6.0: handoff ladder, agy bias suite, permissions fix, akiship activation fix

Added

• coding.B5 — a six-rung ladder a check must fail before it may be handed to the owner (read the flow, search the tree, search vendor docs, probe locally, run it reversibly, only then hand off), each survivor carrying a one-line reason.
• scripts/test-agy-bias.sh — 6-trap regression suite for agy/Gemini helpful-bias and shortcut-bias, 6/6 across two model tiers.
• tauri.B7 — macOS TCC/Gatekeeper boundary for anything a Tauri backend spawns, restored with five factual corrections.

Fixed

• /akiship activation made literal: requires the exact /akiship token plus an imperative turn, closing a gap where a completion-intensity word alone triggered a push.
• agy permission pre-allow rules corrected — the installer's wildcard rules never matched agy's literal-prefix matcher, so every agy /akiflow run was silently denied.
• Repo-wide .md consistency sweep: stale claims, broken relative links, and two backfilled changelog entries for already-shipped fixes.

Full Changelog: 2.5.0...2.6.0

v2.5.0: audit-rename, owner-interrupt kill-tests, trimmed context

Added

• agent.A3 kill-tests: three checks every candidate owner question must survive before it reaches the user — impact, already-authorized, silence-is-not-contradiction (reversibility stays the existing fourth). Evidence: a real council run escalated four self-answerable questions, each killed by one of these tests.
• coding.B3 hand-off ledger: one deduped batch of human-run checks per run, not one per phase.
• README.md gains a Usage model section mapping each working-day moment to its entry point.
• agent.A3 ask-protocol: analyze first, then ask in plain, everyday language.

Changed

• Audit METHOD files renamed audit-first: METHOD-flow-audit.md -> METHOD-audit-flow.md, METHOD-zero-trust-audit.md -> METHOD-audit-zero-trust.md, METHOD-subtraction-audit.md -> METHOD-audit-subtraction.md. Topic addresses (flow/zero-trust/subtract) unchanged.
• akiflow Step 4 and the aki-judge/aki-challenger agents trimmed to pure pointers at the new kill-tests rule instead of restating it.
• install.py sets akihelp to name-only by default (0 lifetime invocations across 461 startups).
• payload/index.md trimmed ~2.3k chars of always-resident session context — the three core-file manifest rows collapsed to a fixed pointer; Project binding and Change policy moved to README.md.

Full Changelog: 2.4.2...2.5.0

v2.4.2: pre-allow skill script permissions

Added

• No more repeated permission prompts when skill scripts run in Claude Code, Antigravity CLI/IDE, or Kiro CLI — the installer now pre-approves them automatically, scoped only to the managed skill folders.
• New reference doc covering permission/allowlist formats across all five supported CLIs.

Full Changelog: 2.4.1...2.4.2

v2.4.1: akiship completion-intensity dial

Changed

• release.B8 gains a completion-intensity dial: /akiship now treats "trọn vẹn" / "hoàn thành, hoàn thiện" / equivalent finish-everything phrasing in the invocation as a signal that collapses the mid-edit-vs-abandoned stop AND authorizes push/tag/GitHub-Release. The owner's ask: the escalation floor's condition (2) — B7 step 0's "undecidable from the tree alone" ambiguity — was firing on ordinary in-progress leftovers even when the owner had explicitly asked for a complete, unattended run, forcing a mid-run question the invocation itself had already answered. B8 now resolves that ambiguity toward mid-edit (finish and integrate) whenever the invocation carries a completion-intensity signal, while conditions (1) public-history ambiguity and (3) design contradiction/scope stay hard stops regardless of phrasing — they gate on irreversibility and correctness, not effort, matching the owner's own carve-out ("trừ khi... nghiêm trọng hoặc mâu thuẫn lớn"). Push/deploy/GitHub-Release were initially left gated separately (agent.B3 — visible to others) since the ask was framed around tree classification, but the owner's intent behind "trọn vẹn"/"full...luôn" was never scoped that narrowly — it meant finish the whole ritual, artifacts included — so the same signal now covers both; a plain /akiship with no intensity marker still stays local-only. skills/akiship/SKILL.md Phase 1 step 3, Phase 3 step 4, its frontmatter description, its Boundaries line, and README.md's akiship row updated with it.
• skills/akirule/SKILL.md Tier keyword tightening (re-audit of the Jun 24 plan against the post-2.4.0 file). Removed ubiquitous bare-word keywords that were loading their rule file on nearly every message — copy, văn bản, pages, plugin, layout, flow, conditional, timing, value, effort, scope, index.md, feat/ — replacing each with a narrower phrase that keeps real coverage: semantic→semantic stability, nội dung→nội dung UI/nội dung giao diện, workers→cloudflare workers/cf workers, plugin→nuxt plugin (with plugins/** added to the stack rule's Paths line), layout→nuxt layout, conditional→nested conditional/điều kiện lồng nhau, timing→timing issue/race condition, scope→scope creep/mở rộng scope, feat/→docs/feat/. Receipt-format consolidation: Tier 2 step 3's [akirule:full] Loaded: <filenames> folded into the single [RULES] … (router:full) line the Load-confirmation section already defines, removing the two-format conflict. Added a skip-if-already-loaded line to the Tier 1 intro so a repeat signal match on a file already read this conversation does not force a redundant Read. Deep-think corrections folded in against the original Jun 24 wording: the stack rule's Default ON condition now names the Aki web stack specifically (a bare "or the akirule skill" clause would have turned it on for every project, including Tauri-only ones, since every project CLAUDE.md references akirule); flow was replaced by luồng xử lý only, not user flow, since that phrase is already a METHOD-ux-psych signal and would have cross-routed; plugin was replaced rather than dropped outright, since the plugins/** path it was meant to be covered by never existed in the Paths line until this change added it.

v2.4.0: add /akiship one-command full release

Added

• New /akiship command runs the full daily release ritual in one shot — leftover triage, doc sync, lint, CHANGELOG, commit, and version — instead of a hand-typed checklist.
• New autonomy contract lets an unattended release run stop only for genuinely undecidable cases (history ambiguity, unclassifiable mid-edit work, or a design conflict) instead of stalling on routine confirmations.

Changed

• The pre-ship gate now also triages leftover/unfinished work first and sweeps only the files actually changed for lint and dead-code issues, keeping full-repo sweeps as a separate on-demand audit.

Full Changelog: 2.3.2...2.4.0

v2.3.2: arch doc drift fix, scythe fenced code block linting, harness quick-facts

Fixed

• Fixed documentation drift in docs/arch/akiflow.md across transcript layout, domain consults, and gate pointers.
• Updated the akiflow architecture diagram to include the dispatch shape and mechanical verification gates.
• Corrected legacy references (akirule-enforcer, gate law #4) in README.md, akilint, and harness-facts.md.
• Enhanced scythe.py to lint comments inside fenced code blocks in markdown.

Changed

• Added a Worker invocation quick-facts lookup table to harness-facts.md with explicit cross-file locks.
• Standardized model tier rules in aki-hands with clear default and escalation boundaries.

Full Changelog: 2.3.1...2.3.2

v2.3.1: fix release title separator, drop dead B6 dash carve-out

Fixed

• Fixed RULE-release.md title template separator from em dash to colon, resolving the B4/B6 self-contradiction.
• Clarified that CI-automated release creation still owes Title and Body content, not --generate-notes alone.

Full Changelog: 2.3.0...2.3.1