@jenga-ai/agent 3.6.0 → 4.1.0

package/skills/j-doc/scripts/resolve_last_update.py

@@ -5,6 +5,7 @@ from __future__ import annotations
 
 import argparse
 import json
+import subprocess
 import sys
 from datetime import date
 from pathlib import Path
@@ -18,6 +19,31 @@ BOARD_DIRS = (
 )
 
 
+def _resolve_project_root() -> Path:
+    """Locate the project root via git, not a fixed relative climb.
+
+    This script is deployed both at its source location
+    (skills/j-doc/scripts/) and mirrored one directory deeper into
+    .claude/skills/j-doc/scripts/ / .agents/skills/j-doc/scripts/ -- a fixed
+    parents[N] climb from __file__ only lands on the real repo root from the
+    source location, not from a mirror. Same approach as
+    skills/j-close-story/scripts/check-story-closeable.sh,
+    check-privatized.sh:138, and compute-scope-divergence.sh:54 use for the
+    equivalent bash case.
+    """
+    try:
+        result = subprocess.run(
+            ["git", "rev-parse", "--show-toplevel"],
+            cwd=Path(__file__).resolve().parent,
+            capture_output=True,
+            text=True,
+            check=True,
+        )
+        return Path(result.stdout.strip())
+    except (subprocess.CalledProcessError, FileNotFoundError, OSError):
+        return Path.cwd()
+
+
 def parse_args() -> argparse.Namespace:
     parser = argparse.ArgumentParser(
         description="Resolve the latest completed board date for a documentation target.",
@@ -25,7 +51,7 @@ def parse_args() -> argparse.Namespace:
     parser.add_argument("target_path", help="Repo-relative documentation target path, e.g. README.md")
     parser.add_argument(
         "--root",
-        default=Path(__file__).resolve().parents[3],
+        default=_resolve_project_root(),
         type=Path,
         help="Repository root containing project/board/",
     )

package/skills/j-doc-sync/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.doc-sync
-description: Polyfill alias of the doc-sync skill under a collision-safe directory name. Identical behavior to /doc-sync — Compare the current state of a project with its documentation and update documentation to reflect changes. Accepts `update:`, `source:`, `exclude:`, and `minify:` arguments to control scope. Use when documentation may be out of date with implementation, or when the user asks to sync, refresh, update, or shrink docs. Use when the bare /doc-sync form is shadowed by another tool's own built-in command of the same name.
+description: Compare the current state of a project with its documentation and update documentation to reflect changes. Accepts `update:`, `source:`, `exclude:`, and `minify:` arguments to control scope. Use when documentation may be out of date with implementation, or when the user asks to sync, refresh, update, or shrink docs.
 output_types: file_list
 keywords:
   - doc-sync
@@ -8,7 +8,6 @@ keywords:
   - update docs
   - sync docs
   - j-doc-sync
-  - polyfill
 examples:
   - "update the documentation"
   - "sync docs with current state"
@@ -17,9 +16,9 @@ examples:
 
 # Doc-Sync — Keep Documentation in Sync with the Codebase
 
-This skill is a literal-directory-name duplicate of `skills/doc-sync/`. It exists so that `/j-doc-sync` (and `j.j-doc-sync`) give a guaranteed-unshadowed way to reach the same flow as `/doc-sync`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/doc-sync` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-doc-sync/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-doc-sync/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh doc-sync` from `skills/doc-sync/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/doc-sync/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## What this skill does
 

package/skills/j-dooo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.dooo
-description: Polyfill alias of the dooo skill under a collision-safe directory name. Identical behavior to /dooo — Parallel execution orchestrator. Calls /do to start implementations via sub-agents, then loops back to the board to identify and offer parallelisable tasks until the user selects "Done". Use when the bare /dooo form is shadowed by another tool's own built-in command of the same name.
+description: Parallel execution orchestrator. Calls /do to start implementations via sub-agents, then loops back to the board to identify and offer parallelisable tasks until the user selects "Done".
 keywords:
   - dooo
   - parallel
@@ -8,7 +8,6 @@ keywords:
   - multiple tasks
   - orchestrate
   - j-dooo
-  - polyfill
 examples:
   - "run all pending tasks in parallel"
   - "execute multiple tasks at once"
@@ -19,32 +18,24 @@ metadata:
 
 # Dooo — Parallel Execution Orchestrator
 
-This skill is a literal-directory-name duplicate of `skills/dooo/`. It exists so that `/j-dooo` (and `j.j-dooo`) give a guaranteed-unshadowed way to reach the same flow as `/dooo`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/dooo` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-dooo/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-dooo/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh dooo` from `skills/dooo/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/dooo/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 
 ### 1. Invoke `/do`
 Call the `/do` skill to let the user select and start an implementation. `/do` will launch a background sub-agent to handle the implementation. Once the sub-agent is launched, `/do` returns control here.
 
-After `/do` hands back control, mark the story/task that was just started as **Running** in its board file (update the `status:` field in the YAML front-matter).
+After `/do` hands back control, mark the story/task that was just started as **In Progress** in its board file (update the `status:` field in the YAML front-matter).
 
 ### 2. Return to the board — identify parallelisable tasks
 
-Collect candidates from two sources:
-
-1. **Stories** — read all files from `project/board/stories/`.
-2. **Tasks derived from stories** — read all files from `project/board/tasks/`. A task is considered in-scope if its parent story (`story_id` in the task's front-matter) is listed in `project/todo.md`, even if the task itself is not directly listed there.
-
-A story or task is **eligible** to be presented as a parallel candidate if ALL of the following are true:
-- Its status is `Pending` (not `Running`, `In Progress`, `Passed`, etc.)
-- It has no unresolved dependencies (all blocking stories/tasks are at least `Running` or `Passed`)
-- It is directly listed in `project/todo.md`, **OR** its parent story is listed in `project/todo.md`
+Run `scripts/render-ranked-list.sh` from the project root. It scans `project/board/stories/` and `project/board/tasks/` against `project/todo.md` and prints the eligible items as a ranked, 1-indexed `<id> — <title>` list (stories first, then tasks) — this is the same eligibility scan and rendering `/dooo` has always used (status `Pending`, no unresolved dependencies, directly listed in `project/todo.md` or — for tasks — parent story listed), now implemented once in a shared script rather than described here as inline prose (`E63_S01_T01`; see `scripts/render-ranked-list.sh`'s own header for the full rule and its env-var overrides). A sibling command, `/todo --ranked-list`, calls the same script for a non-interactive view of this same list.
 
 ### 3. Present choices to the user
 
-Build a numbered list of eligible story titles (use `ask_user` with `choices`). **Always append "Done" as the last option.**
+Relay the script's output as the numbered list (use `ask_user` with `choices`). **Always append "Done" as the last option.**
 
 Example:
 ```

package/skills/j-error/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.error
-description: Polyfill alias of the error skill under a collision-safe directory name. Identical behavior to /error — Guided troubleshooting flow that gathers context about an error — where it occurs, what was attempted, what went wrong, and what was expected. Use when the bare /error form is shadowed by another tool's own built-in command of the same name.
+description: Guided troubleshooting flow that gathers context about an error — where it occurs, what was attempted, what went wrong, and what was expected.
 keywords:
   - error
   - bug
@@ -9,7 +9,6 @@ keywords:
   - debug
   - broken
   - j-error
-  - polyfill
 examples:
   - "I'm getting an error"
   - "help me fix this bug"
@@ -20,9 +19,9 @@ metadata:
 
 # Error — Guided Troubleshooting
 
-This skill is a literal-directory-name duplicate of `skills/error/`. It exists so that `/j-error` (and `j.j-error`) give a guaranteed-unshadowed way to reach the same flow as `/error`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/error` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-error/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-error/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh error` from `skills/error/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/error/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-evaluate/SKILL.md

@@ -1,16 +1,15 @@
 ---
 name: j.evaluate
-description: Polyfill alias of the evaluate skill under a collision-safe directory name. Identical behavior to /evaluate — Analyzes example files against a target goal and produces a structured evaluation rapport. Use when the bare /evaluate form is shadowed by another tool's own built-in command of the same name.
+description: Analyzes example files against a target goal and produces a structured evaluation rapport.
 keywords:
   - j-evaluate
-  - polyfill
 ---
 
 # Evaluate
 
-This skill is a literal-directory-name duplicate of `skills/evaluate/`. It exists so that `/j-evaluate` (and `j.j-evaluate`) give a guaranteed-unshadowed way to reach the same flow as `/evaluate`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/evaluate` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-evaluate/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-evaluate/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh evaluate` from `skills/evaluate/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/evaluate/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Input
 

package/skills/j-examplify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.examplify
-description: Polyfill alias of the examplify skill under a collision-safe directory name. Identical behavior to /examplify — Explains concepts, features, use cases, and patterns based on provided context — a description, scenario, code snippet, or file. Use when the user wants to understand what something is, how it works, when to use it, or wants a concrete example. Use when the bare /examplify form is shadowed by another tool's own built-in command of the same name.
+description: Explains concepts, features, use cases, and patterns based on provided context — a description, scenario, code snippet, or file. Use when the user wants to understand what something is, how it works, when to use it, or wants a concrete example.
 keywords:
   - examplify
   - explain
@@ -8,7 +8,6 @@ keywords:
   - how does
   - understand
   - j-examplify
-  - polyfill
 examples:
   - "explain how this works"
   - "give me an example of X"
@@ -17,9 +16,9 @@ examples:
 
 # Concept Explainer
 
-This skill is a literal-directory-name duplicate of `skills/examplify/`. It exists so that `/j-examplify` (and `j.j-examplify`) give a guaranteed-unshadowed way to reach the same flow as `/examplify`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/examplify` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-examplify/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-examplify/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh examplify` from `skills/examplify/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/examplify/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.help
-description: Polyfill alias of the help skill under a collision-safe directory name. Identical behavior to /help — List all available skills with a short description of what each one does. Also use this skill when the user wants to know what commands or skills are available in the project. Use when the bare /help form is shadowed by another tool's own built-in command of the same name.
+description: List all available skills with a short description of what each one does. Also use this skill when the user wants to know what commands or skills are available in the project.
 keywords:
   - help
   - skills
@@ -8,7 +8,6 @@ keywords:
   - what can you do
   - list skills
   - j-help
-  - polyfill
 examples:
   - "what skills are available?"
   - "show me all commands"
@@ -17,9 +16,9 @@ examples:
 
 # Help — List Available Skills
 
-This skill is a literal-directory-name duplicate of `skills/help/`. It exists so that `/j-help` (and `j.j-help`) give a guaranteed-unshadowed way to reach the same flow as `/help`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/help` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-help/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-help/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh help` from `skills/help/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/help/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-idea/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.idea
-description: Polyfill alias of the idea skill under a collision-safe directory name. Identical behavior to /idea — DEPRECATED - use the prefixed 'j-idea' skill instead. Capture a loosely-defined idea to project/ideas.md — a lightweight, "maybe someday" log with no board or promotion overhead. Use when the bare /idea form is shadowed by another tool's own built-in command of the same name.
+description: Capture a loosely-defined idea to project/ideas.md — a lightweight, "maybe someday" log with no board or promotion overhead.
 keywords:
   - idea
   - capture idea
@@ -8,7 +8,6 @@ keywords:
   - brain dump
   - maybe someday
   - j-idea
-  - polyfill
 examples:
   - "capture this as an idea"
   - "log this idea for later"
@@ -20,9 +19,9 @@ metadata:
 
 # Idea — Lightweight Idea Capture
 
-This skill is a literal-directory-name duplicate of `skills/idea/`. It exists so that `/j-idea` (and `j.j-idea`) give a guaranteed-unshadowed way to reach the same flow as `/idea`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/idea` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-idea/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-idea/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh idea` from `skills/idea/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/idea/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-improve/SKILL.md

@@ -1,16 +1,15 @@
 ---
 name: j.improve
-description: Polyfill alias of the improve skill under a collision-safe directory name. Identical behavior to /improve — A skill for analyzing a codebase and producing a structured improvement plan toward a defined goal. Use when the bare /improve form is shadowed by another tool's own built-in command of the same name.
+description: A skill for analyzing a codebase and producing a structured improvement plan toward a defined goal.
 keywords:
   - j-improve
-  - polyfill
 ---
 
 # Improve
 
-This skill is a literal-directory-name duplicate of `skills/improve/`. It exists so that `/j-improve` (and `j.j-improve`) give a guaranteed-unshadowed way to reach the same flow as `/improve`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/improve` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-improve/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-improve/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh improve` from `skills/improve/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/improve/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.init
-description: Polyfill alias of the init skill under a collision-safe directory name. Identical behavior to /init — initializes a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Use when the built-in "/init" command (e.g. GH Copilot's own init) shadows Jenga's /init alias.
+description: initializes a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Use when the built-in "/init" command (e.g. GH Copilot's own init) shadows Jenga's /init alias.
 keywords:
   - init
   - initialize
@@ -8,7 +8,6 @@ keywords:
   - new project
   - scaffold
   - j-init
-  - polyfill
 examples:
   - "initialize a new project"
   - "set up a new workspace"
@@ -17,15 +16,25 @@ examples:
 
 # J-Init — Project Setup (polyfill alias of Init)
 
-This skill is a literal-directory-name duplicate of `skills/init/`. It exists because
-some host tools/harnesses (e.g. GH Copilot) ship their own built-in command literally
-named `/init`, which can shadow or override Jenga AI's own `/init` alias (Claude Code's
-native skill resolution is a literal-string, directory-name-based match — see
-`docs/skill-authoring.md`'s "Invocation Convention"). `/j-init` (and `j.j-init`) give
-users a guaranteed-unshadowed way to reach the exact same setup flow.
-
-Keep this file's instructions in lockstep with `skills/init/SKILL.md` — any change made
-there should be mirrored here.
+`skills/j-init/` is the **sole canonical directory** for this skill. The `j-` prefix is
+there for collision safety: some host tools/harnesses (e.g. GH Copilot) ship their own
+built-in command literally named `/init`, which would shadow a bare `/init` alias, since
+Claude Code's native skill resolution is a literal-string, directory-name-based match —
+see `docs/skill-authoring.md`'s "Invocation Convention". Invoke it as `j.init` or
+`/j-init`.
+
+> **This file was previously described as a duplicate of `skills/init/`, with an
+> instruction to keep the two in lockstep. That instruction is void.** `E50_S15_T04`
+> deleted every bare-name `skills/<name>/` directory on 2026-09-19, making
+> `skills/j-<name>/` the sole canonical form (see `docs/skill-authoring.md`'s "The
+> Canonical Naming Contract"), and `scripts/generate-j-alias.sh` — which had excluded this
+> hand-maintained pair from generation anyway — was retired by `E50_S14_T01`. There is no
+> second copy to mirror a change into, and none should be created. Edit this file directly.
+>
+> Corrected by `E42_S07_T01`'s follow-up, per
+> `project/rapports/problems/E42_S07_T01-j-init-skill-md-lockstep-instruction-still-stale.md`.
+> The same correction already landed one level down, in
+> `skills/j-init/scripts/apply-scaffold-visibility.sh`.
 
 ## Instructions
 

package/skills/j-init/scripts/apply-scaffold-visibility.sh

@@ -14,12 +14,14 @@
 # skills/j-distribute/CONFIG_SCHEMA.md's "Scaffold visibility" section for the
 # full rationale.
 #
-# This is skills/j-init/'s own copy of skills/init/scripts/apply-scaffold-visibility.sh
-# (E31_S07_T03) — skills/j-init/ is a separate, hand-maintained directory, not
-# auto-synced with skills/init/ (scripts/generate-j-alias.sh explicitly excludes
-# this pair), and is the copy that actually ships to public-GitHub-mirror and
-# npm-package consumers. Keep this file's logic in lockstep with skills/init/'s
-# copy — any behavioral change made there should be mirrored here.
+# This file is the sole copy. It was added by E31_S07_T03 as skills/j-init/'s own
+# hand-maintained duplicate of a then-existing skills/init/scripts/ copy, with an
+# instruction to keep the two in lockstep. That instruction is void: E50_S15_T04
+# deleted every bare-name skills/<name>/ directory on 2026-09-19, making
+# skills/j-<name>/ the sole canonical form (see docs/skill-authoring.md's "The
+# Canonical Naming Contract"), and scripts/generate-j-alias.sh — which had excluded
+# this pair from generation as hand-maintained — was itself retired by E50_S14_T01.
+# There is no second copy to mirror a change into, and none should be created.
 #
 # Usage:
 #   apply-scaffold-visibility.sh <mode> [project_root]

package/skills/j-jbp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.jbp
-description: Polyfill alias of the jbp skill under a collision-safe directory name. Identical behavior to /jbp — Scaffold the project using the JengaBasePlate boilerplate repo template from https://github.com/samwelmunga/JengaBasePlate.git. Use when the bare /jbp form is shadowed by another tool's own built-in command of the same name.
+description: Scaffold the project using the JengaBasePlate boilerplate repo template from https://github.com/samwelmunga/JengaBasePlate.git.
 keywords:
   - jbp
   - boilerplate
@@ -8,7 +8,6 @@ keywords:
   - template
   - jenga base
   - j-jbp
-  - polyfill
 examples:
   - "scaffold with JengaBasePlate"
   - "set up the base template"
@@ -17,9 +16,9 @@ examples:
 
 # JBP — JengaBasePlate Scaffold
 
-This skill is a literal-directory-name duplicate of `skills/jbp/`. It exists so that `/j-jbp` (and `j.j-jbp`) give a guaranteed-unshadowed way to reach the same flow as `/jbp`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/jbp` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-jbp/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-jbp/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh jbp` from `skills/jbp/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/jbp/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-lgtm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.lgtm
-description: Polyfill alias of the lgtm skill under a collision-safe directory name. Identical behavior to /lgtm — Approve and commit the current work, then continue to the next task. Shortcut that chains /commit followed by /continue. Use when the bare /lgtm form is shadowed by another tool's own built-in command of the same name.
+description: Approve and commit the current work, then continue to the next task. Shortcut that chains /commit followed by /continue.
 keywords:
   - lgtm
   - approve
@@ -8,7 +8,6 @@ keywords:
   - done
   - commit and continue
   - j-lgtm
-  - polyfill
 examples:
   - "lgtm, commit this"
   - "looks good, move on"
@@ -17,9 +16,9 @@ examples:
 
 # LGTM — Approve, Commit, and Continue
 
-This skill is a literal-directory-name duplicate of `skills/lgtm/`. It exists so that `/j-lgtm` (and `j.j-lgtm`) give a guaranteed-unshadowed way to reach the same flow as `/lgtm`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/lgtm` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-lgtm/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-lgtm/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh lgtm` from `skills/lgtm/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/lgtm/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-pi-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.pi-plan
-description: Polyfill alias of the pi-plan skill under a collision-safe directory name. Identical behavior to /pi-plan — Define or expand project Epics in PROJECT_SUMMARY.md. Use this at the start of a project to establish its foundation, AND whenever the user wants to add major new features, plan a significant new area of work, or make epic-level changes to an existing project. Trigger whenever you hear things like "new feature area", "big change", "new epic", "expand the project", "add a major capability", or "plan a new phase" — even mid-project. Use when the bare /pi-plan form is shadowed by another tool's own built-in command of the same name.
+description: Define or expand project Epics in PROJECT_SUMMARY.md. Use this at the start of a project to establish its foundation, AND whenever the user wants to add major new features, plan a significant new area of work, or make epic-level changes to an existing project. Trigger whenever you hear things like "new feature area", "big change", "new epic", "expand the project", "add a major capability", or "plan a new phase" — even mid-project.
 keywords:
   - epic
   - template
@@ -8,7 +8,6 @@ keywords:
   - new feature area
   - project structure
   - j-pi-plan
-  - polyfill
 examples:
   - "add a new epic for X"
   - "expand the project with a new feature area"
@@ -19,9 +18,9 @@ metadata:
 
 # Pi-plan — Define and Expand Project Epics
 
-This skill is a literal-directory-name duplicate of `skills/pi-plan/`. It exists so that `/j-pi-plan` (and `j.j-pi-plan`) give a guaranteed-unshadowed way to reach the same flow as `/pi-plan`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/pi-plan` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-pi-plan/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-pi-plan/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh pi-plan` from `skills/pi-plan/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/pi-plan/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## When to use this skill
 

package/skills/j-proceed/SKILL.md

@@ -1,13 +1,12 @@
 ---
 name: j.proceed
-description: Polyfill alias of the proceed skill under a collision-safe directory name. Identical behavior to /proceed — Review project progress by checking epics and stories, optionally consulting PROJECT_SUMMARY.md and WARP.md, then continue executing the project plan. Use when the bare /proceed form is shadowed by another tool's own built-in command of the same name.
+description: Review project progress by checking epics and stories, optionally consulting PROJECT_SUMMARY.md and WARP.md, then continue executing the project plan.
 keywords:
   - proceed
   - review progress
   - check epics
   - continue executing
   - j-proceed
-  - polyfill
 examples:
   - "proceed with the plan"
   - "review progress and continue"
@@ -18,9 +17,9 @@ metadata:
 
 # Proceed — Resume Project Execution
 
-This skill is a literal-directory-name duplicate of `skills/proceed/`. It exists so that `/j-proceed` (and `j.j-proceed`) give a guaranteed-unshadowed way to reach the same flow as `/proceed`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/proceed` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-proceed/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-proceed/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh proceed` from `skills/proceed/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/proceed/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-publish/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.publish
-description: Polyfill alias of the publish skill under a collision-safe directory name. Identical behavior to /publish — Configure, validate, and orchestrate scaffolded release workflows through a single `/publish` entry point with bounded sub-commands. Use when the bare /publish form is shadowed by another tool's own built-in command of the same name.
+description: Configure, validate, and orchestrate scaffolded release workflows through a single `/publish` entry point with bounded sub-commands.
 keywords:
   - publish
   - deploy
@@ -12,7 +12,6 @@ keywords:
   - staged publishing
   - stage
   - j-publish
-  - polyfill
 examples:
   - "publish setup --target staging-appstore"
   - "publish setup --type mobile-ios"
@@ -42,9 +41,9 @@ metadata:
 
 # Publish — Deployment Pipeline Orchestrator
 
-This skill is a literal-directory-name duplicate of `skills/publish/`. It exists so that `/j-publish` (and `j.j-publish`) give a guaranteed-unshadowed way to reach the same flow as `/publish`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/publish` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-publish/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-publish/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh publish` from `skills/publish/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/publish/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 `/publish` is the single entry point for release workflows in this repository. It wires configuration validation, setup, gated deployment, release-note drafting, and ledger history into one end-to-end flow, and dispatches the final publish step to a per-type adapter.
 

package/skills/j-publish/scripts/run_gates.sh

@@ -292,7 +292,7 @@ run_command_capture() {
   local command="$1"
   LAST_GATE_COMMAND="$command"
   set +e
-  RUN_OUTPUT="$(bash -lc "$command" 2>&1)"
+  RUN_OUTPUT="$(bash -c "$command" 2>&1)"
   RUN_STATUS=$?
   set -e
 }