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.