docs(claude-design): state the no-CI substitute, drop the private-file pointer

Two judgement findings from the repo-standard skill that its script cannot
measure, both on the presentation surface:

- Verification named the whole-suite command but not the fact that nothing
  runs it automatically. The skill treats a stated single command plus that
  admission as the honest substitute for a CI badge; this repo has no CI
  config of any kind, so say so.
- The Changelog section sent a public reader to `REMEMBER.md` for the v1.0
  readiness criteria. That file is gitignored, is not present, and is a
  retired local-continuity mechanism — so the pointer resolved to nothing
  for every reader. The criteria were already inline in the same sentence;
  keep them and drop the pointer.

Gate: repo-standard v0.2.0 reports OK, 14/14, no SKIP.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B4DrFX1ubxrmswAH3rwSeN
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 11:53:25 +02:00
commit 692d47f421

View file

@ -241,6 +241,8 @@ When Anthropic publishes per-preset guidance for a Community-only or Experimenta
bash verify.sh
```
Nothing runs this automatically — there is no CI in this repository. The command above is the entire suite, and it runs from a clean clone with no setup step.
Runs five test scripts under `tests/` in dependency order:
| Script | Verifies |
@ -293,7 +295,7 @@ Full release history: [CHANGELOG.md](CHANGELOG.md). The plugin follows [Semantic
**v0.1.0 — 2026-05-17.** Initial public release. Single skill (`claude-design-facilitator`) with eight-phase facilitation flow, 12 natural-language trigger phrases, 13 reference files (5 foundation + 8 per-preset with evidence-grade labels), `.coverage.md` preset manifest plus Authoritative-claims registry, five verification scripts under `tests/` enforcing structural integrity / scope fence / skill description quality / per-preset coverage / Anthropic-domain citation discipline / operator dogfood log format, top-level `verify.sh` roll-up with `--strict` and `--quick` flags, MIT license, GOVERNANCE.md fork-and-own model.
The path from v0.1 to v1.0 is dogfood-driven — see the plugin's `REMEMBER.md` (local-only, gitignored) for the v1.0 readiness criteria (multi-preset breadth, auto-fire validation in real natural-language requests, two consecutive dogfood sessions with zero critical patches).
The path from v0.1 to v1.0 is dogfood-driven. The v1.0 readiness criteria are multi-preset breadth, auto-fire validation in real natural-language requests, and two consecutive dogfood sessions with zero critical patches. The dogfood log itself is operator-local and never published.
---