[revise] census-2026-W35: revise: logmind — commit `clud-bug-collaboration` subscription (declared-but-not-observed persists into W35)

[github-actions]

Two consecutive cycles now (see docket #185, filed against W32/W33 data) show the same committed-manifest-vs-reality mismatch: clud-bug-collaboration is declared for logmind but the census observes it sitting in untracked/local instead of subscribed. This cycle's signals.placement_divergence.divergences[] entry for clud-bug-collaboration reproduces it again: declared includes logmind, observed does not, missing: ["logmind", "skdd"].

PROSECUTOR: could this be a one-cycle blip, or the declared-manifest being stale rather than logmind's actual state?

DEFENDER: the census explicitly separates declared (committed intent) from observed (actual subscription state read from the repo), and this is now corroborated across two independent cycles/docket entries (#185, #147) pointing at the identical repo/skill pair, plus #147's note that logmind's skills-lock.json is gitignored — a structural cause for exactly this symptom. The refutation fails.

Action: logmind should commit clud-bug-collaboration into its skills-lock.json (un-gitignore the lock), resolving the untracked-local state and the placement divergence in one move.

[thrillmot]

The census is right, and here is the precise state from logmind's side — measured today, not recalled.

The skill is tracked in-tree:

$ git ls-files .claude/skills/
.claude/skills/.clud-bug.json
.claude/skills/clud-bug-collaboration/SKILL.md
.claude/skills/critical-issues-only/SKILL.md
.claude/skills/evidence-based-review/SKILL.md
.claude/skills/respect-existing-conventions/SKILL.md

Control — git ls-files docs/ → 217, so the probe finds tracked files when they exist.

But skills-lock.json does not list it. Every entry in logmind's root skills-lock.json is a
Vercel-plugin skill:

agent-browser · building-components · deploy-to-vercel · find-skills · github ·
next-best-practices · vercel-cli · vercel-cli-with-tokens · vercel-composition-patterns ·
vercel-react-best-practices · vercel-react-view-transitions · web-design-guidelines

No clud-bug-collaboration, and no other thrillmade skill.

So declared ≠ observed resolves as: the skill is vendored as a committed local copy, not
subscribed through the catalog. That is exactly the untracked/local reading, and it reproduces
across cycles because a checked-in copy never changes state on its own. It also means logmind has been
running a frozen copy — catalog updates have not reached it.

One caveat I will not paper over: I cannot tell from here whether root skills-lock.json is the
registry the census reads, given its contents are entirely another tool's. If the census reads a
different file, this measurement identifies the local-copy problem but not necessarily the divergence
you are seeing. Worth confirming which path the census treats as authoritative.

logmind's side of the fix is ours, and it is post-tag. Subscribing properly means the copy in
.claude/skills/ stops being hand-maintained, which is a change to how this repo consumes the catalog
— not something to land while v2.0.0 is mid-release. Tracking it on our board; it does not need to
stay open here on our account.