thachvd-kit 1.0.37 → 1.0.39

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "thachvd-kit",
-    "version": "1.0.37",
+    "version": "1.0.39",
     "description": "Cross-agent project rules bootstrap kit for Codex, Antigravity, and Claude Code",
     "bin": {
         "thachvd-kit": "./bin/entry.js"
@@ -17,8 +17,8 @@
         "node": ">=16.7"
     },
     "scripts": {
-        "test": "node test/cli.test.js && node test/policy.test.js && node test/matt-skills.test.js && node test/native-skills.test.js && node test/upgrade.test.js && node test/global.test.js",
-        "release:verify": "npm test && node --check bin/cli.js && node --check bin/entry.js && node --check bin/policy.js && node --check bin/matt-skills.js && node --check bin/native-skills.js && node --check bin/upgrade.js && node --check bin/global.js && node --check skills/subagent-driven-development/scripts/sdd-workspace-lib.js && node --check skills/subagent-driven-development/scripts/sdd-workspace.js && node --check skills/subagent-driven-development/scripts/task-brief.js && node --check skills/subagent-driven-development/scripts/review-package.js && npm pack --dry-run",
+        "test": "node test/config.test.js && node test/cli.test.js && node test/spec.test.js && node test/spec-state.test.js && node test/spec-doctor.test.js && node test/spec-site.test.js && node test/spec-recipe.test.js && node test/spec-link.test.js && node test/policy.test.js && node test/matt-skills.test.js && node test/native-skills.test.js && node test/upgrade.test.js && node test/global.test.js",
+        "release:verify": "npm test && node --check bin/cli.js && node --check bin/config.js && node --check bin/entry.js && node --check bin/spec.js && node --check bin/spec-state.js && node --check bin/spec-doctor.js && node --check bin/spec-site.js && node --check bin/spec-recipe.js && node --check bin/spec-link.js && node --check bin/policy.js && node --check bin/matt-skills.js && node --check bin/native-skills.js && node --check bin/upgrade.js && node --check bin/global.js && node --check skills/subagent-driven-development/scripts/sdd-workspace-lib.js && node --check skills/subagent-driven-development/scripts/sdd-workspace.js && node --check skills/subagent-driven-development/scripts/task-brief.js && node --check skills/subagent-driven-development/scripts/review-package.js && npm pack --dry-run",
         "preversion": "npm run release:verify",
         "release:patch": "npm version patch",
         "release:dry-run": "npm pack --dry-run",

package/skills/finishing-a-development-branch/SKILL.md

@@ -1,240 +1,240 @@
----
-name: finishing-a-development-branch
-description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
----
-
-# Finishing a Development Branch
-
-## Overview
-
-**Core principle:** Verify tests → Detect environment → Present options → Execute choice → Clean up.
-
-**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."
-
-## Step 1: Verify Tests
-
-Run the project's full test suite using the documented project command (for example, one of `npm test`, `cargo test`, `pytest`, or `go test ./...`).
-
-**If tests fail**, report the failures and stop — the menu comes after a green suite:
-
-```
-Tests failing (<N> failures). Must fix before completing:
-
-[Show failures]
-```
-
-**If tests pass:** continue to Step 2.
-
-## Step 2: Determine Workspace Provenance
-
-Determine whether implementation happened in-place or in a task-created isolated workspace. Use the implementation handoff, plan, or conversation as the source of truth:
-
-- **In-place:** the user chose the current branch/workspace, or the existing workspace was reused without creating a branch/worktree for this task. This includes an explicitly requested direct change on `main` or another named branch.
-- **Task-created isolated workspace:** this workflow or an explicitly requested `/using-git-worktrees` flow created the branch/worktree for this task.
-- **Unknown:** do not infer task ownership from a named branch, a non-default branch, or Git topology alone. Treat it as in-place unless the human confirms that this task created the branch/worktree.
-
-For an in-place workspace, after tests pass report the verified current branch/workspace and hand off. Do not determine a base branch, offer a self-merge, remove the current branch, or remove the current worktree. Pushing or opening a PR remains a separate explicit user decision.
-
-```text
-Implementation complete in the current workspace on `<branch>`. Tests pass.
-No merge or branch/worktree cleanup is needed. The current branch is ready for handoff.
-```
-
-Only continue to the environment and integration menu below for a task-created isolated workspace.
-
-## Step 3: Detect Environment
-
-```text
-git rev-parse --git-dir
-git rev-parse --git-common-dir
-git rev-parse --show-toplevel
-git rev-parse --show-superproject-working-tree
-git branch --show-current
-git worktree list --porcelain
-```
-
-Compare the first two results rather than relying on Bash path normalization. Capture the repository root and worktree path before changing directories. This determines which menu to show and how cleanup works:
-
-| State | Menu | Cleanup |
-|-------|------|---------|
-| `--git-dir` equals `--git-common-dir` (normal repo) | Standard 3 options | No worktree to clean up |
-| Values differ, named branch, not a submodule | Standard 3 options | Provenance-based (see Step 7) |
-| Values differ, detached HEAD | Reduced 2 options (no merge) | Externally managed — leave in place |
-
-## Step 4: Determine Base Branch
-
-The base branch is whatever this work forked from — usually named in the
-plan, the conversation, or the branch's upstream. If it is not already
-known, ask: "This branch split from <your best guess> - is that correct?"
-Confirm before merging: merging into the wrong base is expensive to undo.
-
-## Step 5: Present Options
-
-**Normal repo and named-branch worktree — present exactly these 3 options:**
-
-```
-Implementation complete. What would you like to do?
-
-1. Merge back to <base-branch> locally
-2. Push and create a Pull Request
-3. Keep the branch as-is (I'll handle it later)
-
-Which option?
-```
-
-**Detached HEAD — present exactly these 2 options:**
-
-```
-Implementation complete. You're on a detached HEAD (externally managed workspace).
-
-1. Push as new branch and create a Pull Request
-2. Keep as-is (I'll handle it later)
-
-Which option?
-```
-
-Present the menu exactly as written — concise, with every option coming
-from the list above. Discarding the work happens only in response to your
-human partner explicitly asking for it (see "If your human partner asks to
-discard the work" below). Wait for their answer; the integration decision
-is theirs.
-
-## Step 6: Execute Choice
-
-### Option 1: Merge Locally
-
-```text
-# From the main repository root, after confirming the base branch:
-git rev-parse --show-toplevel
-git switch <base-branch>
-git pull
-git merge <feature-branch>
-
-# Verify tests on merged result
-<test command>
-```
-
-If tests fail on the merged result: stop, leave the worktree and branch in
-place, and investigate — nothing has been pushed, so the merge is local
-and recoverable.
-
-Once the merged result is green: clean up the worktree (Step 7), then
-delete the branch:
-
-```bash
-git branch -d <feature-branch>
-```
-
-### Option 2: Push and Create PR
-
-```bash
-git push -u origin <feature-branch>
-# From a detached HEAD, name the new branch on the remote:
-# git push origin HEAD:refs/heads/<new-branch>
-```
-
-Then create the pull/merge request against <base-branch> with the forge's
-tooling — its CLI if one is available, or the creation URL most forges
-print when you push — following the repo's PR template and conventions if
-present, and report the URL to your human partner.
-
-Keep the worktree — your human partner iterates on PR feedback there.
-
-### Option 3: Keep As-Is
-
-Report: "Keeping branch <name>. Worktree preserved at <path>."
-
-### If your human partner asks to discard the work
-
-This path exists only as a response to an explicit request to throw the
-work away. Confirm first:
-
-```
-This will permanently delete:
-- Branch <name>
-- All commits: <commit-list>
-- Worktree at <path>
-
-Type 'discard' to confirm.
-```
-
-Wait for that exact confirmation. When it arrives:
-
-```text
-# From the main repository root, after explicit discard confirmation:
-git rev-parse --show-toplevel
-```
-
-Then clean up the worktree (Step 7) and force-delete the branch:
-
-```bash
-git branch -D <feature-branch>
-```
-
-## Step 7: Cleanup Workspace
-
-**Runs for Option 1 and confirmed discards.** Options 2 and 3 always
-preserve the worktree. Both callers have already changed directory to the
-main repo root — worktree removal must run from outside the worktree —
-and use the Git directory/common-directory comparison and worktree path captured
-in Step 2, from before that directory change.
-
-**If `--git-dir` equals `--git-common-dir`:** Normal repo, no worktree to clean up. Done.
-
-**If the captured worktree path is under `.worktrees/` or `worktrees/`:** This
-workflow owns the manually managed project-local worktree and may clean it up:
-
-```bash
-git worktree remove "<captured-worktree-path>"
-git worktree prune  # Self-healing: clean up any stale registrations
-```
-
-**If removal is refused** (`contains modified or untracked files`): the
-worktree holds files that exist nowhere else — uncommitted plans, notes,
-or scratch work. Never `--force` on your own initiative. Show your human
-partner what is at stake and ask:
-
-```bash
-git -C "<captured-worktree-path>" status --porcelain -uall
-```
-
-```
-Worktree removal refused — these files were never committed:
-
-<file list>
-
-1. Commit them to <branch> before cleanup
-2. Move them into <main repo root>
-3. Delete them (unrecoverable)
-
-Which?
-```
-
-Carry out the choice, then remove the worktree.
-
-**Otherwise:** The host environment owns this workspace — leave it in
-place. If your platform provides a workspace-exit tool, use it.
-
-## Quick Reference
-
-| Option | Merge | Push | Keep Worktree | Cleanup Branch |
-|--------|-------|------|---------------|----------------|
-| 1. Merge locally | yes | - | - | yes |
-| 2. Create PR | - | yes | yes | - |
-| 3. Keep as-is | - | - | yes | - |
-| Discard (explicit request only) | - | - | - | yes (force) |
-
-## Common Rationalizations
-
-| Excuse | Reality |
-|--------|---------|
-| "Tests passed earlier this session" | Run the suite on the tree you are about to integrate. A green run only proves the tree it ran on. |
-| "They obviously want it merged" | Integration is your human partner's decision. Present the menu and wait. |
-| "They seem done with this feature — I'll offer to discard it" | The menu is complete as written. Discard happens only when your human partner asks for it in so many words. |
-| "'Yeah, get rid of it' counts as confirmation" | Only the typed word `discard` authorizes deletion. |
-| "The PR is up, so the worktree is clutter now" | PR feedback gets fixed in that worktree. It stays until the work lands. |
-| "This other worktree looks stale — I'll clean it too" | Clean up only worktrees under `.worktrees/` or `worktrees/`. Everything else belongs to the host. |
-| "Removal refused — `--force` is just finishing the cleanup" | The refusal means files exist only in that worktree. `--force` destroys them permanently. Show your human partner and ask. |
-| "The merged-result failure is probably flaky" | A failing merged result stops everything. Branch and worktree stay put while you investigate. |
-| "The base branch is obviously main" | Confirm the fork point or ask. Merging into the wrong base is expensive to undo. |
-| "The push was rejected — force-push will fix it" | A rejected push means the remote moved. Investigate; force-push only on your human partner's explicit request. |
+---
+name: finishing-a-development-branch
+description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
+---
+
+# Finishing a Development Branch
+
+## Overview
+
+**Core principle:** Verify tests → Detect environment → Present options → Execute choice → Clean up.
+
+**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."
+
+## Step 1: Verify Tests
+
+Run the project's full test suite using the documented project command (for example, one of `npm test`, `cargo test`, `pytest`, or `go test ./...`).
+
+**If tests fail**, report the failures and stop — the menu comes after a green suite:
+
+```
+Tests failing (<N> failures). Must fix before completing:
+
+[Show failures]
+```
+
+**If tests pass:** continue to Step 2.
+
+## Step 2: Determine Workspace Provenance
+
+Determine whether implementation happened in-place or in a task-created isolated workspace. Use the implementation handoff, plan, or conversation as the source of truth:
+
+- **In-place:** the user chose the current branch/workspace, or the existing workspace was reused without creating a branch/worktree for this task. This includes an explicitly requested direct change on `main` or another named branch.
+- **Task-created isolated workspace:** this workflow or an explicitly requested `/using-git-worktrees` flow created the branch/worktree for this task.
+- **Unknown:** do not infer task ownership from a named branch, a non-default branch, or Git topology alone. Treat it as in-place unless the human confirms that this task created the branch/worktree.
+
+For an in-place workspace, after tests pass report the verified current branch/workspace and hand off. Do not determine a base branch, offer a self-merge, remove the current branch, or remove the current worktree. Pushing or opening a PR remains a separate explicit user decision.
+
+```text
+Implementation complete in the current workspace on `<branch>`. Tests pass.
+No merge or branch/worktree cleanup is needed. The current branch is ready for handoff.
+```
+
+Only continue to the environment and integration menu below for a task-created isolated workspace.
+
+## Step 3: Detect Environment
+
+```text
+git rev-parse --git-dir
+git rev-parse --git-common-dir
+git rev-parse --show-toplevel
+git rev-parse --show-superproject-working-tree
+git branch --show-current
+git worktree list --porcelain
+```
+
+Compare the first two results rather than relying on Bash path normalization. Capture the repository root and worktree path before changing directories. This determines which menu to show and how cleanup works:
+
+| State | Menu | Cleanup |
+|-------|------|---------|
+| `--git-dir` equals `--git-common-dir` (normal repo) | Standard 3 options | No worktree to clean up |
+| Values differ, named branch, not a submodule | Standard 3 options | Provenance-based (see Step 7) |
+| Values differ, detached HEAD | Reduced 2 options (no merge) | Externally managed — leave in place |
+
+## Step 4: Determine Base Branch
+
+The base branch is whatever this work forked from — usually named in the
+plan, the conversation, or the branch's upstream. If it is not already
+known, ask: "This branch split from <your best guess> - is that correct?"
+Confirm before merging: merging into the wrong base is expensive to undo.
+
+## Step 5: Present Options
+
+**Normal repo and named-branch worktree — present exactly these 3 options:**
+
+```
+Implementation complete. What would you like to do?
+
+1. Merge back to <base-branch> locally
+2. Push and create a Pull Request
+3. Keep the branch as-is (I'll handle it later)
+
+Which option?
+```
+
+**Detached HEAD — present exactly these 2 options:**
+
+```
+Implementation complete. You're on a detached HEAD (externally managed workspace).
+
+1. Push as new branch and create a Pull Request
+2. Keep as-is (I'll handle it later)
+
+Which option?
+```
+
+Present the menu exactly as written — concise, with every option coming
+from the list above. Discarding the work happens only in response to your
+human partner explicitly asking for it (see "If your human partner asks to
+discard the work" below). Wait for their answer; the integration decision
+is theirs.
+
+## Step 6: Execute Choice
+
+### Option 1: Merge Locally
+
+```text
+# From the main repository root, after confirming the base branch:
+git rev-parse --show-toplevel
+git switch <base-branch>
+git pull
+git merge <feature-branch>
+
+# Verify tests on merged result
+<test command>
+```
+
+If tests fail on the merged result: stop, leave the worktree and branch in
+place, and investigate — nothing has been pushed, so the merge is local
+and recoverable.
+
+Once the merged result is green: clean up the worktree (Step 7), then
+delete the branch:
+
+```bash
+git branch -d <feature-branch>
+```
+
+### Option 2: Push and Create PR
+
+```bash
+git push -u origin <feature-branch>
+# From a detached HEAD, name the new branch on the remote:
+# git push origin HEAD:refs/heads/<new-branch>
+```
+
+Then create the pull/merge request against <base-branch> with the forge's
+tooling — its CLI if one is available, or the creation URL most forges
+print when you push — following the repo's PR template and conventions if
+present, and report the URL to your human partner.
+
+Keep the worktree — your human partner iterates on PR feedback there.
+
+### Option 3: Keep As-Is
+
+Report: "Keeping branch <name>. Worktree preserved at <path>."
+
+### If your human partner asks to discard the work
+
+This path exists only as a response to an explicit request to throw the
+work away. Confirm first:
+
+```
+This will permanently delete:
+- Branch <name>
+- All commits: <commit-list>
+- Worktree at <path>
+
+Type 'discard' to confirm.
+```
+
+Wait for that exact confirmation. When it arrives:
+
+```text
+# From the main repository root, after explicit discard confirmation:
+git rev-parse --show-toplevel
+```
+
+Then clean up the worktree (Step 7) and force-delete the branch:
+
+```bash
+git branch -D <feature-branch>
+```
+
+## Step 7: Cleanup Workspace
+
+**Runs for Option 1 and confirmed discards.** Options 2 and 3 always
+preserve the worktree. Both callers have already changed directory to the
+main repo root — worktree removal must run from outside the worktree —
+and use the Git directory/common-directory comparison and worktree path captured
+in Step 2, from before that directory change.
+
+**If `--git-dir` equals `--git-common-dir`:** Normal repo, no worktree to clean up. Done.
+
+**If the captured worktree path is under `.worktrees/` or `worktrees/`:** This
+workflow owns the manually managed project-local worktree and may clean it up:
+
+```bash
+git worktree remove "<captured-worktree-path>"
+git worktree prune  # Self-healing: clean up any stale registrations
+```
+
+**If removal is refused** (`contains modified or untracked files`): the
+worktree holds files that exist nowhere else — uncommitted plans, notes,
+or scratch work. Never `--force` on your own initiative. Show your human
+partner what is at stake and ask:
+
+```bash
+git -C "<captured-worktree-path>" status --porcelain -uall
+```
+
+```
+Worktree removal refused — these files were never committed:
+
+<file list>
+
+1. Commit them to <branch> before cleanup
+2. Move them into <main repo root>
+3. Delete them (unrecoverable)
+
+Which?
+```
+
+Carry out the choice, then remove the worktree.
+
+**Otherwise:** The host environment owns this workspace — leave it in
+place. If your platform provides a workspace-exit tool, use it.
+
+## Quick Reference
+
+| Option | Merge | Push | Keep Worktree | Cleanup Branch |
+|--------|-------|------|---------------|----------------|
+| 1. Merge locally | yes | - | - | yes |
+| 2. Create PR | - | yes | yes | - |
+| 3. Keep as-is | - | - | yes | - |
+| Discard (explicit request only) | - | - | - | yes (force) |
+
+## Common Rationalizations
+
+| Excuse | Reality |
+|--------|---------|
+| "Tests passed earlier this session" | Run the suite on the tree you are about to integrate. A green run only proves the tree it ran on. |
+| "They obviously want it merged" | Integration is your human partner's decision. Present the menu and wait. |
+| "They seem done with this feature — I'll offer to discard it" | The menu is complete as written. Discard happens only when your human partner asks for it in so many words. |
+| "'Yeah, get rid of it' counts as confirmation" | Only the typed word `discard` authorizes deletion. |
+| "The PR is up, so the worktree is clutter now" | PR feedback gets fixed in that worktree. It stays until the work lands. |
+| "This other worktree looks stale — I'll clean it too" | Clean up only worktrees under `.worktrees/` or `worktrees/`. Everything else belongs to the host. |
+| "Removal refused — `--force` is just finishing the cleanup" | The refusal means files exist only in that worktree. `--force` destroys them permanently. Show your human partner and ask. |
+| "The merged-result failure is probably flaky" | A failing merged result stops everything. Branch and worktree stay put while you investigate. |
+| "The base branch is obviously main" | Confirm the fork point or ask. Merging into the wrong base is expensive to undo. |
+| "The push was rejected — force-push will fix it" | A rejected push means the remote moved. Investigate; force-push only on your human partner's explicit request. |