@erclx/aitk 0.65.1 → 0.66.0

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "aitk",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "0.65.1",
+  "version": "0.66.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "0.65.1",
+  "version": "0.66.0",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/scripts/core/check-seed-independence.sh

@@ -0,0 +1,59 @@
+#!/usr/bin/env bash
+set -e
+set -o pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="${PROJECT_ROOT:-$(cd "$SCRIPT_DIR/../.." && pwd)}"
+
+source "$PROJECT_ROOT/scripts/lib/tooling.sh"
+
+TOOLKIT_TOKEN="aitk"
+TOOLING_ROOT="$PROJECT_ROOT/tooling"
+
+# `find` writes to stderr and returns non-zero for a missing root, inside a
+# process substitution whose status nothing reads. Without this the walk covers
+# nothing and the check reports the seeds independent having never read one.
+if [ ! -d "$TOOLING_ROOT" ]; then
+  echo "No tooling root at ${TOOLING_ROOT#"$PROJECT_ROOT/"}, seed independence unverifiable." >&2
+  exit 1
+fi
+
+# An empty discovery is a real state rather than a broken walk, and the Seed
+# standards stage already reports it as a skip. Failing here would have the two
+# stages disagree about what the same condition means.
+seed_roots=$(collect_seed_roots)
+if [ -z "$seed_roots" ]; then
+  echo "No seed root carries .claude/, nothing to check." >&2
+  exit 0
+fi
+
+# Markdown alone. The seed tree also ships hooks that call the toolkit CLI on
+# purpose, each reporting a named stale-index warning when the binary is absent,
+# and scoping by extension leaves them outside this walk without an exemption
+# list that would have to be maintained against them.
+cited=""
+measured=0
+while IFS= read -r seed_root; do
+  while IFS= read -r file; do
+    measured=$((measured + 1))
+    while IFS= read -r hit; do
+      cited="$cited  ${file#"$PROJECT_ROOT/"}:$hit"$'\n'
+    done < <(grep -n "$TOOLKIT_TOKEN" "$file" || true)
+  done < <(find "$PROJECT_ROOT/$seed_root" -type f -name '*.md')
+done <<<"$seed_roots"
+
+# Roots resolved and no markdown under any of them is a walk that covered
+# nothing, which is the verdict-without-a-measurement the guards above refuse for
+# a missing tree. Reporting a pass here would say the seeds cite no CLI on the
+# strength of having read no prose.
+if [ "$measured" -eq 0 ]; then
+  echo "Seed roots resolved but carry no markdown, seed independence unverifiable." >&2
+  exit 1
+fi
+
+if [ -n "$cited" ]; then
+  echo "Seed prose cites the toolkit CLI:" >&2
+  printf '%s' "$cited" >&2
+  echo "A scaffolded project may not have $TOOLKIT_TOKEN installed. State the capability the line needs rather than the binary that supplies it." >&2
+  exit 1
+fi

package/scripts/core/verify.sh

@@ -7,6 +7,7 @@ PROJECT_ROOT="${PROJECT_ROOT:-$(cd "$SCRIPT_DIR/../.." && pwd)}"
 
 source "$PROJECT_ROOT/scripts/lib/ui.sh"
 source "$PROJECT_ROOT/scripts/lib/worktree.sh"
+source "$PROJECT_ROOT/scripts/lib/tooling.sh"
 
 NESTED="${VERIFY_NESTED:-false}"
 WRITE="${VERIFY_WRITE:-true}"
@@ -127,16 +128,6 @@ assert_hero_pair() {
   [ "$html_commit" = "$png_commit" ]
 }
 
-# Whatever stacks the repo currently carries, so a new one is covered without an
-# edit here. A seed root holding no `.claude/` seeds nothing a standard governs.
-collect_seed_roots() {
-  local dir
-  for dir in "$PROJECT_ROOT"/tooling/*/seeds; do
-    [ -d "$dir/.claude" ] || continue
-    printf '%s\n' "${dir#"$PROJECT_ROOT"/}"
-  done
-}
-
 # Entries the audit actually measured, summed across the folders it resolved.
 # `--json` carries one `"entries":<n>` per folder object, and the top-level key
 # of that name holds an array, so the numeric match reaches folders alone.
@@ -214,6 +205,15 @@ main() {
   run_check "bash $PROJECT_ROOT/scripts/core/check-plugin-boundary.sh" "Plugin ships toolkit-internal content."
   log_info "Plugin boundary clean"
 
+  # Seed prose is installed into every scaffolded project and read there as
+  # instruction about that project, so a line naming this repository's CLI hands
+  # a target a verb it may not be able to run. This gates for the reason the
+  # Seed standards stage below gates: a defect authored once propagates into
+  # every project scaffolded after it.
+  log_step "Seed independence"
+  run_check "bash $PROJECT_ROOT/scripts/core/check-seed-independence.sh" "Seed prose cites the toolkit CLI."
+  log_info "Seed prose cites no toolkit CLI"
+
   # A stack entry naming a rule folder takes every rule in it, which is what
   # stops a new rule from needing a second edit to reach a target. The failure
   # it leaves open is a rule authored into a folder no stack names, which

package/scripts/lib/tooling.sh

@@ -22,3 +22,14 @@ list_tooling_stacks() {
     echo "$name"
   done < <(find "$tooling_dir" -mindepth 1 -maxdepth 1 -type d | sort)
 }
+
+# Seed roots that carry a `.claude/`, emitted relative to `PROJECT_ROOT`. Every
+# stage measuring seed content discovers through this rather than naming a stack,
+# so a stack seeding `.claude/` later arrives covered with no edit to any caller.
+collect_seed_roots() {
+  local dir
+  for dir in "$PROJECT_ROOT"/tooling/*/seeds; do
+    [ -d "$dir/.claude" ] || continue
+    printf '%s\n' "${dir#"$PROJECT_ROOT"/}"
+  done
+}

package/tooling/claude/seeds/CLAUDE.md

@@ -74,7 +74,7 @@
 - Write all memory files to `.claude/memory/`, not `~/.claude/projects/`
 - A fact about a domain goes to that domain's `.claude/context/` entry, not to memory. `claude-memory-capture` routes it there and `claude-docs` folds it in. Memory keeps only what no context entry owns.
 - Never delete a memory entry. Retire one by moving it to `.claude/.tmp/memory-archive/`. A bulk retire runs through the shell, where no file edit fires a path-scoped rule, and the folder is gitignored with nothing to recover from.
-- Follow `.claude/standards/memory.md` for the filename and type prefix, the frontmatter, the body shape each type carries, and the lifecycle. Run `aitk records validate memory` to check the pen against it.
+- Follow `.claude/standards/memory.md` for the filename and type prefix, the frontmatter, the body shape each type carries, and the lifecycle. Check every entry in the pen against that standard and fix what breaks it, since nothing keeps the folder conforming on its own.
 
 ## Scratch
 
@@ -87,4 +87,4 @@
 - From a linked worktree, every `Edit` or `Write` to a tracked file (source, docs) must use a path starting with `pwd`.
 - From a linked worktree, `Edit` and `Write` are refused for every main-root path, session scratch included. The refusal names session isolation and points at the worktree copy, which is a second gitignored file no later session reads, so never take that redirect.
 - `Read` resolves against the main root normally from a linked worktree. A main-root write reaches it only through `Bash`, as one plain command rather than a compound one, which is refused for complexity.
-- Route a main-root write by what it does to the file. Creating a whole file goes out as one plain `Bash` command carrying a heredoc. Changing a line inside a file that already exists goes through an `aitk` verb, which resolves the main root in-process, because the shell route for that case is the stream editor this file bans.
+- Route a main-root write by what it does to the file. Creating a whole file goes out as one plain `Bash` command carrying a heredoc. Changing a line inside a file that already exists goes through a command that resolves the main root in-process, because the shell route for that case is the stream editor this file bans.