sync: auto-sync from GURU-5070 at 2026-07-01 15:06:42

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-07-01 15:06:42
This commit is contained in:
2026-07-01 15:07:34 -07:00
parent 875048f9ad
commit c3aeef60fb
24 changed files with 200 additions and 191 deletions

View File

@@ -0,0 +1,115 @@
# 2026-07-01 — /self-check run + skill-registry description trim (GREEN)
## User
- **User:** Mike Swanson (mike)
- **Machine:** GURU-5070
- **Role:** admin
## Session Summary
Ran `/self-check` (the fleet-conformance probe) on GURU-5070. The deterministic probe graded
AMBER: 83 PASS, 1 WARN, 0 FAIL, 35 INFO against provisional manifest 1.0.0. The single warning
was `harness.registry_budget` — the sum of all repo SKILL.md frontmatter `description:` fields
was 15,658 chars against the 10,500 budget (35 skills), i.e. registry bloat taxing every
session's context load.
Ran both semantic passes the skill mandates on a full check. Pass 1 (rogue-memory
contradiction vs identity.json/settings): clean. The one suspect — `feedback_ollama_tier0_routing.md`
headlining qwen3:14b while this box's identity.json sets `prose_model: qwen3:8b` — self-resolves:
the memory body instructs reading `prose_model` from identity.json and documents that 12 GB boxes
like GURU-5070 get 8b (its Python example hardcoding 'qwen3:14b' is cosmetic only).
Pass 2 (command-vs-standard): `time-entry-protocol.md` still defers to `/syncro` as SSOT and both
agree add_line_item is normal billing with timers outlier-only — no drift.
Mike asked to trim the descriptions and re-publish. Measured with the probe's own awk logic
(frontmatter-only, description block until next top-level key). Trimmed 23 skills' descriptions
from multi-paragraph essays to single ~250-290 char lines, keeping distinctive trigger keywords
and gating notes. Before cutting, verified every load-bearing fact (tenant IDs, endpoints,
communityId 622, azcomp4587, B2 accountId, cmdkey/SYSTEM gotchas, SQLX_OFFLINE, etc.) already
exists in each SKILL.md body — nothing lost, only deduplicated. Registry total: 15,658 -> 9,786
chars (~700 headroom).
Copied the 23 trimmed SKILL.md files to `~/.claude/skills/` so the repo-vs-global duplicate
check stays "identical" rather than flipping to divergent-WARN. Re-ran with `--publish`:
**Grade GREEN** (84 PASS / 0 WARN / 0 FAIL / 35 INFO), census published to coord as component
`selfcheck_GURU-5070 = GREEN`.
## Key Decisions
- Trimmed descriptions in-place with a Python script implementing the probe's exact awk
counting logic (frontmatter description block only), rather than eyeballing — the first
naive measurement (whole-file grab) wildly overcounted and would have led to wrong targets.
- Kept distinctive trigger keywords in every trimmed description (skill routing depends on
them); moved nothing that wasn't already duplicated in the SKILL.md body.
- Verified body coverage of load-bearing facts (grep per key fact) BEFORE deleting them from
frontmatter, instead of blindly relocating text.
- Trimmed 4 extra skills (mailprotector, rmm-audit, remediation-tool, gitea) beyond the
minimum needed, to build ~700 chars of headroom so the next added skill doesn't re-trip
the WARN.
- Synced trimmed files to `~/.claude/skills/` immediately to avoid creating repo/global
divergence (the "same skill, different behavior" failure the duplicates check exists for).
- Semantic memory pass: judged from MEMORY.md index one-liners + targeted file reads instead
of opening all ~200 memory files; only opened the one genuine suspect.
## Problems Encountered
- Initial description measurement (awk over whole file with `head -50`) gave ~80k total vs the
probe's 15,658 — the probe counts ONLY the frontmatter description block between the `---`
markers. Resolved by reading `check_harness_smoke()` in
`.claude/skills/self-check/scripts/self-check.sh` and reusing its exact awk.
- First trim pass landed at 10,272/10,500 — technically passing but with only ~230 chars
headroom. Trimmed 4 more skills to reach 9,786.
## Configuration Changes
Modified (frontmatter description trimmed to one line; body untouched), in BOTH
`.claude/skills/<name>/SKILL.md` and `~/.claude/skills/<name>/SKILL.md`:
- agy, alis, b2, bitdefender, coord, datto-edr, discord-dm, drive-map, frontend-design,
gitea, grok, gururmm-build, mailprotector, onboard365, packetdial, remediation-tool,
rmm-audit, rmm-search, screenconnect, synology, unifi-wifi, vault, yealink-ymcs
(23 skills)
Created:
- `session-logs/2026-07/2026-07-01-mike-self-check-skill-desc-trim.md` (this log)
Scratch (session temp dir, not in repo): `trim_descs.py` (the trim script).
## Credentials & Secrets
None surfaced, created, or rotated.
## Infrastructure & Servers
- Coord API `http://172.16.3.30:8001` — reachable; census published as component
`selfcheck_GURU-5070`, state GREEN.
- Capability tier: ollama_local (Ollama 0.30.11 at localhost:11434, fallback Beast
100.101.122.4:11434, prose_model qwen3:8b). cargo/node/gh/op present; docker absent
(capability off, expected).
## Commands & Outputs
- Probe: `SELFCHECK_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)" bash .claude/skills/self-check/scripts/self-check.sh report` -> AMBER, sole WARN `harness.registry_budget` (15658 > 10500).
- Per-skill budget measurement: probe's awk (frontmatter `description:` block, stop at next
`^[A-Za-z0-9_-]+:` or closing `---`), summed over `.claude/skills/*/SKILL.md`.
- Re-run + publish: `... self-check.sh --publish` -> GREEN, `[OK] Published census to coord: component selfcheck_GURU-5070 = GREEN`.
## Pending / Incomplete Tasks
- The 23 trimmed SKILL.md files sync fleet-wide with this /save's commit; other machines
re-run `/self-check` after pulling to clear their own registry_budget WARN and republish.
- Baseline manifest still provisional (1.0.0): 25 skills + 4 commands report as census
candidates — ratification of `baseline/manifest.json` (via fanout + aggregate) still ahead.
- Standing INFO: 27 commands + 35 skills duplicated repo vs `~/.claude` (identical today;
probe flags divergence if it happens). Docker absent — deliberate.
## Reference Information
- Probe engine: `.claude/skills/self-check/scripts/self-check.sh` (budget logic in
`check_harness_smoke()`, ~line 588).
- Baseline: `.claude/skills/self-check/baseline/manifest.json``harness.registry_desc_budget_chars: 10500`;
`command_standard_links` has one pair (syncro-billing: `.claude/standards/syncro/time-entry-protocol.md`
must defer to `/syncro`) — verified intact and non-contradictory.
- Registry description totals: before 15,658 / after 9,786 (budget 10,500).
- Semantic pass artifacts checked: `.claude/memory/feedback_ollama_tier0_routing.md`,
`.claude/standards/syncro/time-entry-protocol.md`, `.claude/commands/syncro.md`.