xtrm-tools 0.7.0 → 0.7.2

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/with_skill/outputs/result.md

@@ -1,237 +0,0 @@
-# sync-docs Eval: Sprint Closeout
-
-**Task:** "I just closed a bunch of bd issues this sprint and merged 3 PRs. The README.md is getting long — can you sync the docs and make sure everything's in order? Use sync-docs."
-
-**Date:** 2026-03-18
-**Working directory:** `/home/dawid/projects/xtrm-tools`
-
----
-
-## Mandatory First Step: Serena Activation
-
-The skill requires activating the Serena project first:
-
-```javascript
-mcp__serena__activate_project({ project: "/home/dawid/projects/xtrm-tools" })
-```
-
-Serena MCP was not available in this environment (`mcp__serena__*` tools not present). This step was noted but could not be executed. All Phase 4 doc edits are flagged as "Serena would be used here" rather than executed directly.
-
----
-
-## Phase 1: Gather Context
-
-**Script:** `python3 skills/sync-docs/scripts/context_gatherer.py --since=30`
-
-**Status:** SUCCESS — ran from repo path (script not installed at `~/.claude/skills/sync-docs/`; skill has not been installed via `xtrm install`)
-
-### Key Findings
-
-**bd closed issues (20 in last 30 days):**
-- 7x P0 bugs: dead code removal, commit gate fix, quality gates wiring, hash drift detection fix, main-guard Serena bypass, legacy hook cleanup, MCP sync guard fix
-- 13x P1 tasks/bugs: hook injection retirement, Pi extensions audit, branch protection bug, blocking protocol fix, documentation update, beads statusline fix, main-guard Bash handler, beads.ts Pi commit gate, global hook registration (quality-gates, service-skills), global skills sync, xtrm init, architecture tests
-
-**Merged PRs (git history, last 30 days — most recent 3):**
-- PR #15: release/2.0.1 (2026-03-13)
-- PR #14: chore/update-status-doc (2026-03-13)
-- PR #13: fix/agents-target (2026-03-13)
-
-**Recent commits (today, 2026-03-18):**
-- Centralize guard tool rules and matcher expansion
-- Deprecate install project command in favor of xtrm init
-- Add global-first architecture regression tests
-- Add project detection and service registry scaffolding to xtrm init
-- Promote service and quality skills to global sync set
-- Make service-skills extension CWD-aware and global
-- Move quality gates to global Claude hooks
-
-**bd memories available:** 20 entries — architecture decisions around beads gate, Pi session key, claude plugin workflow, blocking protocol format, etc.
-
-**Serena drift check (from script):** `available: false` — context_gatherer delegates this to drift_detector.py which requires `yaml` module.
-
----
-
-## Phase 2: Detect SSOT Drift
-
-**Script:** `python3 ~/.claude/skills/documenting/scripts/drift_detector.py scan`
-
-**Status:** SUCCESS (with workaround — required `pip install pyyaml --break-system-packages` due to externally-managed Python environment)
-
-### Key Findings: 5 Stale Serena Memories
-
-| Memory | Last Updated | Modified Files |
-|---|---|---|
-| `ssot_cli_hooks_2026-02-03` | 2026-02-25 | `hooks/guard-rules.mjs`, `hooks/hooks.json`, `hooks/main-guard.mjs` |
-| `ssot_cli_universal_hub_2026-02-19` | 2026-02-25 | `cli/src/tests/policy-parity.test.ts`, `cli/src/commands/install-project.ts` |
-| `ssot_cli_ux_improvements_2026-02-22` | 2026-02-25 | `cli/src/commands/install-project.ts` |
-| `ssot_jaggers-agent-tools_installer_architecture_2026-02-03` | 2026-02-25 | `cli/src/tests/policy-parity.test.ts`, `cli/src/commands/install-project.ts` |
-| `ssot_jaggers-agent-tools_migration_2026-02-01` | 2026-02-01 | `cli/src/tests/policy-parity.test.ts`, `cli/src/commands/install-project.ts` |
-
-All 5 stale memories are due to changes in `hooks/` and `cli/src/` — consistent with the sprint's P0 bug fixes and architectural refactors.
-
-**Recommended Phase 4 action:** Update all 5 memories using Serena tools (not Edit). Priority: `ssot_cli_hooks_*` due to guard-rules.mjs centralization commit today.
-
----
-
-## Phase 3: Analyze Document Structure
-
-**Script:** `python3 skills/sync-docs/scripts/doc_structure_analyzer.py`
-
-**Status:** PARTIAL SUCCESS — exit code 1 (due to `docs_gaps` detection returning issues count > 0), but full JSON report was produced.
-
-### README.md
-
-| Field | Value |
-|---|---|
-| Status | OK |
-| Line count | 192 / 200 threshold |
-| Sections | 24 |
-| Extraction candidates | None flagged |
-
-README is 192 lines — 8 lines under the 200-line bloat threshold. The user's concern that it is "getting long" is valid but technically not yet `BLOATED` by the script's threshold. **No extraction is required yet**, but it is approaching the limit.
-
-### CHANGELOG.md
-
-| Field | Value |
-|---|---|
-| Status | OK |
-| Last entry date | 2026-03-12 |
-| Last commit date | 2026-03-18 |
-| Issues | None flagged (script) |
-
-**Note:** The script flagged this as OK, but manual inspection shows the CHANGELOG has no entries since 2026-03-12, while git shows 15+ commits today (2026-03-18) including a v2.4.0 release, quality gates wiring, MCP sync guard fix, plugin migration guide, and global-first architecture work. The CHANGELOG is substantively stale relative to the sprint's output. The script's "OK" verdict appears to rely only on the `[Unreleased]` section — it doesn't detect that recent merged PRs with versioned commits (v2.4.0) have no corresponding CHANGELOG section.
-
-### docs/ Gaps
-
-No missing files flagged — the expected files (hooks.md, pi-extensions.md, policies.md, mcp-servers.md) all exist.
-
-### Existing docs/ Status
-
-| File | Status | Line Count | Issue |
-|---|---|---|---|
-| `docs/hooks.md` | INVALID_SCHEMA | 106 | Missing YAML frontmatter |
-| `docs/mcp-servers.md` | OK | 25 | — |
-| `docs/mcp.md` | INVALID_SCHEMA | 84 | Missing YAML frontmatter |
-| `docs/pi-extensions.md` | OK | 25 | — |
-| `docs/policies.md` | OK | 25 | — |
-| `docs/pre-install-cleanup.md` | INVALID_SCHEMA | 107 | Missing YAML frontmatter |
-| `docs/project-skills.md` | INVALID_SCHEMA | 78 | Missing YAML frontmatter |
-| `docs/skills.md` | INVALID_SCHEMA | 89 | Missing YAML frontmatter |
-| `docs/testing.md` | INVALID_SCHEMA | 125 | Missing YAML frontmatter |
-| `docs/todo.md` | INVALID_SCHEMA | 4 | Missing YAML frontmatter |
-
-7 out of 10 docs/ files are missing YAML frontmatter. The files have content (markdown headings, sections) but were never scaffolded with the required schema.
-
----
-
-## Phase 4: Decisions and Actions
-
-### Decision Table
-
-| Finding | Decision | Action |
-|---|---|---|
-| README at 192 lines (near threshold) | Monitor — no extraction yet | Log warning; re-check after next sprint |
-| CHANGELOG last entry 2026-03-12, v2.4.0 not reflected | Update CHANGELOG | Add entries for v2.4.0 and sprint P0 fixes via `add_entry.py` |
-| 5 stale Serena memories | Update with Serena tools | Use `mcp__serena__replace_symbol_body` + bump version + regenerate INDEX |
-| 7 docs/ files missing frontmatter | Add YAML frontmatter | Use `validate_doc.py --generate` scaffold + Serena to insert |
-| `docs/todo.md` (4 lines) | Investigate — possibly remove or expand | Content is placeholder-only |
-| `docs/mcp.md` + `docs/mcp-servers.md` | Consolidate? | Two MCP docs exist; mcp.md has no frontmatter and 84 lines — consider merging into mcp-servers.md |
-
-### Actions Taken
-
-**CHANGELOG update (recommended, not executed — Serena required for doc edits):**
-
-```bash
-python3 ~/.claude/skills/documenting/scripts/changelog/add_entry.py \
-  CHANGELOG.md Added "v2.4.0: Global-first architecture — quality gates and service-skills promoted to global sync, xtrm init project detection, guard rules centralization"
-
-python3 ~/.claude/skills/documenting/scripts/changelog/add_entry.py \
-  CHANGELOG.md Fixed "P0: MCP sync guard placement, hash-based drift detection misclassification, commit gate stale-claim bug, dead code removal (cli/index.js)"
-```
-
-**docs/ frontmatter scaffolding (recommended, Serena required):**
-
-For each of the 7 failing files, the skill instructs generating a scaffold first:
-
-```bash
-python3 skills/sync-docs/scripts/validate_doc.py --generate docs/hooks.md \
-  --title "Hooks Reference" --scope "hooks" --category "reference" \
-  --source-for "hooks/**/*.mjs,hooks/hooks.json"
-
-python3 skills/sync-docs/scripts/validate_doc.py --generate docs/skills.md \
-  --title "Skills Catalog" --scope "skills" --category "reference" \
-  --source-for "skills/**/*"
-
-# (repeat for mcp.md, pre-install-cleanup.md, project-skills.md, testing.md, todo.md)
-```
-
-Then use `mcp__serena__insert_after_symbol` to prepend frontmatter into each file.
-
-**Stale memory updates (Serena required):**
-
-```javascript
-// For ssot_cli_hooks_2026-02-03 — reflect guard-rules.mjs centralization and Bash matcher fix
-mcp__serena__find_symbol({ name: "ssot_cli_hooks_2026-02-03", include_body: true })
-mcp__serena__replace_symbol_body({ symbol_name: "...", new_body: "..." })
-// bump version: patch (content fix) and update `updated:` to 2026-03-18
-```
-
-**bd remember (after structural work):**
-
-```bash
-bd remember "docs/ audit: 7/10 files missing frontmatter, 5 Serena memories stale (hooks + CLI installer arch), CHANGELOG missing v2.4.0 sprint entries. README at 192 lines — not yet bloated." --key sync-docs-audit-2026-03-18
-```
-
----
-
-## Phase 5: Validate
-
-**Script:** `python3 skills/sync-docs/scripts/validate_doc.py /home/dawid/projects/xtrm-tools/docs/`
-
-**Status:** FAILED (exit code 1)
-
-**Result: 3/10 files passed**
-
-| File | Result |
-|---|---|
-| `docs/mcp-servers.md` | PASS |
-| `docs/pi-extensions.md` | PASS |
-| `docs/policies.md` | PASS |
-| `docs/hooks.md` | FAIL — missing frontmatter |
-| `docs/mcp.md` | FAIL — missing frontmatter |
-| `docs/pre-install-cleanup.md` | FAIL — missing frontmatter |
-| `docs/project-skills.md` | FAIL — missing frontmatter |
-| `docs/skills.md` | FAIL — missing frontmatter |
-| `docs/testing.md` | FAIL — missing frontmatter |
-| `docs/todo.md` | FAIL — missing frontmatter |
-
-Validation cannot pass until frontmatter is added to the 7 failing files. This is the primary open action item.
-
----
-
-## Summary of Findings
-
-| Category | Finding | Severity |
-|---|---|---|
-| docs/ schema | 7/10 files missing YAML frontmatter | HIGH — blocks validate_doc.py |
-| Serena memories | 5 stale (hooks, CLI installer arch, UX, migration) | HIGH — AI context drift |
-| CHANGELOG | Missing v2.4.0 and all 2026-03-18 sprint entries | MEDIUM |
-| README | 192 lines — near 200-line threshold | LOW — monitor |
-| MCP docs | Two overlapping files (mcp.md + mcp-servers.md) | LOW — consolidation candidate |
-| docs/todo.md | 4 lines, no frontmatter, likely placeholder | LOW — review or remove |
-
----
-
-## Issues with the Skill Instructions
-
-1. **Script path assumes installed location.** The skill says `python3 "$HOME/.claude/skills/sync-docs/scripts/..."` but the scripts are only in the repo at `skills/sync-docs/scripts/`. If the skill is not installed via `xtrm install`, the path fails. The skill should document the fallback path or require installation first.
-
-2. **drift_detector.py requires `pyyaml` — not in stdlib.** The CLAUDE.md states "Standard library only (no external deps for hooks)" but `drift_detector.py` imports `yaml`. This breaks on clean systems with externally-managed Python (Fedora, macOS with Homebrew). The script should use `tomllib` (3.11+) or a pure-stdlib frontmatter parser, or document the dependency explicitly.
-
-3. **Serena dependency is a hard blocker.** All Phase 4 doc edits require Serena (`mcp__serena__*`). If Serena MCP is not configured, Phase 4 cannot be executed at all. The skill should note a fallback (e.g., manual Edit tool with explicit warning) rather than leaving the phase entirely blocked.
-
-4. **CHANGELOG "OK" verdict is misleading.** The script returns OK for CHANGELOG because an `[Unreleased]` section exists, but does not detect that a versioned release (v2.4.0 via `chore: release v2.4.0` commit) has no corresponding dated section. The gap between last dated entry (2026-03-12) and today's 15+ commits is invisible to the script.
-
-5. **`context_gatherer.py` reports `serena_drift: available: false`** — the embedded drift check silently fails when `yaml` is unavailable, returning an empty result instead of an error. This masks drift data in the Phase 1 report.
-
-6. **`doc_structure_analyzer.py` exits 1 even on informational output.** The exit code 1 fires because `summary.needs_attention: true`, but the JSON report is complete and useful. A shell caller treating non-zero as failure would suppress the output. The script should exit 0 with the report and only exit 1 on actual script errors.

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/with_skill/run-1/grading.json

@@ -1,28 +0,0 @@
-{
-  "eval_id": 1,
-  "run": "with_skill",
-  "expectations": [
-    {
-      "text": "Ran context_gatherer.py and reported bd closed issues or merged PRs from the output",
-      "passed": true,
-      "evidence": "Ran context_gatherer.py, reported 20 bd closed issues with IDs and titles, 3 merged PRs with SHAs and dates, 15 recent commits"
-    },
-    {
-      "text": "Ran doc_structure_analyzer.py and used its output to identify doc issues",
-      "passed": true,
-      "evidence": "Ran doc_structure_analyzer.py, referenced MISSING status for docs/pi-extensions.md, hooks.md, mcp-servers.md, policies.md, skills.md and EXTRACTABLE for README"
-    },
-    {
-      "text": "Produced at least one concrete recommendation or action (not just a vague summary)",
-      "passed": true,
-      "evidence": "Named specific files: docs/pi-extensions.md, docs/hooks.md, docs/mcp-servers.md, docs/policies.md with explicit next steps for each"
-    },
-    {
-      "text": "Used the skill scripts rather than just reading files manually",
-      "passed": true,
-      "evidence": "Ran 3 scripts (context_gatherer.py, drift_detector.py, doc_structure_analyzer.py) with explicit output included in report"
-    }
-  ],
-  "summary": { "passed": 4, "failed": 0, "total": 4, "pass_rate": 1.0 },
-  "notes": "Strong run. Correctly handled missing global install by using local path. Gracefully noted Serena unavailability. One issue: ran drift_detector.py but it required pyyaml pip install — skill should note this fallback."
-}

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/with_skill/run-1/timing.json

@@ -1 +0,0 @@
-{"total_tokens": 32027, "duration_ms": 160761, "total_duration_seconds": 160.8}

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/without_skill/outputs/result.md

@@ -1,134 +0,0 @@
-# Doc Sync Report — Sprint Closeout (2026-03-18)
-
-## What Was Done
-
-Reviewed all primary documentation files against recent git history to assess accuracy and identify gaps after sprint work on the `feature/jaggers-agent-tools-4xr6` branch.
-
-**Tools and sources consulted:**
-- `git log --oneline` (full history + branch-only)
-- `git log --name-only main..HEAD` (files changed per branch commit)
-- Read: `README.md`, `CHANGELOG.md`, `XTRM-GUIDE.md`, `ROADMAP.md`, `AGENTS.md`
-- `package.json` and `cli/package.json` for current version
-- `ls skills/` for skills catalog comparison
-- No `bd` (beads) CLI was run — no `.beads/` DB was found in this repo root
-
----
-
-## Branch Summary (main..HEAD, 7 commits)
-
-| Commit | Change |
-|--------|--------|
-| `54d9978` | Centralize guard tool rules and matcher expansion (guard-rules.mjs, hooks.json, policies) |
-| `f8e37f9` | Deprecate `install project` command in favor of `xtrm init` (XTRM-GUIDE + install-project.ts) |
-| `c1d5182` | Add global-first architecture regression tests |
-| `d83384e` | Add project detection and service registry scaffolding to `xtrm init` |
-| `e35fa46` | Promote service and quality skills to global sync set (multiple skills + scripts) |
-| `b6c057f` | Make service-skills extension CWD-aware and global |
-| `02fe064` | Move quality gates to global Claude hooks |
-
----
-
-## Documentation Issues Found
-
-### 1. Version Mismatch — README.md and XTRM-GUIDE.md out of date
-
-**Severity: High**
-
-- `package.json` reports version **2.4.1**
-- `cli/package.json` reports version **2.4.1**
-- `README.md` header says **Version 2.3.0** (line 5) and the version history table tops out at 2.3.0
-- `XTRM-GUIDE.md` also says **Version 2.3.0** (line 2) and version history tops at 2.3.0
-- `XTRM-GUIDE.md` plugin.json snippet hardcodes `"version": "2.3.0"` (line ~122)
-
-The CHANGELOG shows `[2.4.0]` was released (commit `10d6433: chore: release v2.4.0 (#110)`), but no `[2.4.0]` section exists in `CHANGELOG.md`. The current `package.json` is already at 2.4.1. The CHANGELOG's `[Unreleased]` section contains items that were landed before the 2.4.0 release tag.
-
-### 2. CHANGELOG [Unreleased] Section Is Stale / Missing Branch Changes
-
-**Severity: High**
-
-The `[Unreleased]` section in `CHANGELOG.md` documents:
-- `AGENTS.md` bd section
-- `xtrm install project all`
-- Claude-only target detection fix
-- Project-skill install-all regression tests
-
-None of the 7 branch commits are captured in `[Unreleased]`. The following shipped changes are undocumented:
-- Quality gates moved to global Claude hooks (`02fe064`)
-- Service-skills extension made CWD-aware and global (`b6c057f`)
-- Global service and quality skills promotion (`e35fa46`)
-- `xtrm init` project detection + service registry scaffolding (`d83384e`)
-- Global-first architecture regression tests (`c1d5182`)
-- `install project` command deprecation (`f8e37f9`)
-- Guard tool rules centralized into `guard-rules.mjs` (`54d9978`)
-
-There is also no `[2.4.0]` or `[2.4.1]` section — the release commit exists in git but was never written to the changelog.
-
-### 3. README.md CLI Commands Table — Stale Entry
-
-**Severity: Medium**
-
-`README.md` line 99 lists:
-```
-| `install project <name>` | Install project skill |
-```
-Commit `f8e37f9` explicitly deprecates this command in favor of `xtrm init`. The XTRM-GUIDE was updated (correctly showing it as `**Deprecated**`), but README.md was not updated and still presents this as a live command without any deprecation note. `xtrm init` / `project init` are absent from the README command table entirely.
-
-### 4. README.md Version History Table Capped at 2.3.0
-
-**Severity: Medium**
-
-The Version History table at the bottom of README.md shows:
-```
-| 2.3.0 | 2026-03-17 | Plugin structure, policy compiler, Pi extension parity |
-```
-There is no row for 2.4.0 or 2.4.1.
-
-### 5. ROADMAP.md "Completed in v2.1.9" — Outdated Header
-
-**Severity: Low**
-
-The ROADMAP's completed section header says `Completed in v2.1.9 (2026-03-15)`. There is no section for work completed in v2.4.x, even though multiple roadmap items relate to global-first architecture (quality gates global, service skills global) that are now shipped.
-
-### 6. XTRM-GUIDE.md Skills Catalog — Likely Accurate
-
-**Severity: None (verified OK)**
-
-The skills catalog in XTRM-GUIDE.md (lines 227-252) was updated recently in commit `9f1b1c1 (docs(xtrm-guide): fix skills catalog, Pi events, policy table, version history)`. It lists all skills found under `skills/` including new global skills like `creating-service-skills`, `scoping-service-skills`, `updating-service-skills`, `using-quality-gates`, and `using-service-skills`. This is up to date.
-
-### 7. XTRM-GUIDE.md Policy Table — Matches Current State
-
-**Severity: None (verified OK)**
-
-The policy table in XTRM-GUIDE includes `service-skills.json` (pi, order 40) which was added in `b6c057f`. This is accurate.
-
-### 8. XTRM-GUIDE.md Pi Extensions Table — Includes service-skills.ts
-
-**Severity: None (verified OK)**
-
-`service-skills.ts` is listed as a Pi extension. Consistent with the current state.
-
----
-
-## Summary of Gaps
-
-| File | Gap | Severity |
-|------|-----|----------|
-| `README.md` | Version badge/header says 2.3.0, should be 2.4.1 | High |
-| `README.md` | CLI table missing `xtrm init`, `project init`; `install project` not marked deprecated | Medium |
-| `README.md` | Version History table missing 2.4.0 and 2.4.1 rows | Medium |
-| `XTRM-GUIDE.md` | Version header says 2.3.0, should be 2.4.1 | High |
-| `XTRM-GUIDE.md` | plugin.json snippet shows 2.3.0 | Low |
-| `CHANGELOG.md` | No `[2.4.0]` or `[2.4.1]` sections; release exists in git only | High |
-| `CHANGELOG.md` | All 7 branch commits undocumented | High |
-| `ROADMAP.md` | No completed entry for v2.4.x work | Low |
-
----
-
-## Recommended Next Steps (not done — no commits made)
-
-1. **Promote `[Unreleased]` to `[2.4.0]`** in CHANGELOG.md, add a `[2.4.1]` section for the branch's changes, then add a new empty `[Unreleased]` section at the top.
-2. **Update README.md**: change version badge to 2.4.1, update CLI commands table to add `xtrm init` and mark `install project` as deprecated, add 2.4.0/2.4.1 rows to Version History.
-3. **Update XTRM-GUIDE.md**: change version header and plugin.json snippet to 2.4.1.
-4. **Update ROADMAP.md**: add a `Completed in v2.4.x (2026-03-18)` block listing the global-first architecture work.
-
-No files were modified. No commits were made.

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/without_skill/run-1/grading.json

@@ -1,28 +0,0 @@
-{
-  "eval_id": 1,
-  "run": "without_skill",
-  "expectations": [
-    {
-      "text": "Ran context_gatherer.py and reported bd closed issues or merged PRs from the output",
-      "passed": false,
-      "evidence": "Did not run context_gatherer.py. Used git log manually. Reported 'No .beads/ DB was found' which is wrong — .beads/ exists. Missed all 20 closed bd issues."
-    },
-    {
-      "text": "Ran doc_structure_analyzer.py and used its output to identify doc issues",
-      "passed": false,
-      "evidence": "Did not run doc_structure_analyzer.py. Manually read README.md, package.json, and CHANGELOG.md."
-    },
-    {
-      "text": "Produced at least one concrete recommendation or action (not just a vague summary)",
-      "passed": true,
-      "evidence": "Found version mismatch (2.3.0 vs 2.4.1 in package.json), identified 7 undocumented branch commits in CHANGELOG, named specific line references."
-    },
-    {
-      "text": "Used the skill scripts rather than just reading files manually",
-      "passed": false,
-      "evidence": "No skill scripts were used. All findings came from manual git log, file reads, and README inspection."
-    }
-  ],
-  "summary": { "passed": 1, "failed": 3, "total": 4, "pass_rate": 0.25 },
-  "notes": "The baseline found real value (version mismatch, CHANGELOG staleness) but missed the bd context entirely and produced a different kind of audit than the skill — focused on consistency checking rather than structural doc management."
-}

package/plugins/xtrm-tools/skills/sync-docs-workspace/iteration-1/eval-sprint-closeout/without_skill/run-1/timing.json

@@ -1 +0,0 @@
-{"total_tokens": 50241, "duration_ms": 130768, "total_duration_seconds": 130.8}