fix(docs): links point to the release tag, and no private skill is named #446

Outside the plan: Pascal assigned this card on 2026-11-03, through the grooming of Epic 16. Its pull request says that it is outside the plan.

Problem

An extension pins one release of the nicely template. But the template has 44 links to blob/main. The nicely-extensions skill (extensions/skill/nicely-extensions/SKILL.md) has 3 more, and ncly serves that skill verbatim (extensions/skill/bundled.go lines 15-29). So a pinned extension reads the documentation of main, which can differ from its release. Also, template/.agents/skills/nicely-extension/replace-a-file.md line 52 names create-formal-verification-skill, which is a private skill of Pascal.

Goal

An extension links to the documentation of its own release and names only public tools.

Acceptance rules

1. Each link to the nicely repository in the template renders with the revision that Copier selected (_commit). A render from a release tag gives that tag.
2. The bundled nicely-extensions skill shows links with the tag of the running ncly. A development build shows main.
3. replace-a-file.md describes the step in its own words and names no private skill.
4. A check in just check fails when the template or the bundled skill has a blob/main link to the nicely repository.

Examples

• Success: an extension rendered from template v0.27.0 links to blob/v0.27.0/..., and ncly skill view nicely-extensions of release v0.27.0 shows the same tag.
• Failure: a rendered link or a link of the released skill points to blob/main/... or to another tag.

Check

• scripts/template-test.sh renders the template and finds only links with the rendered tag.
• A test of the bundled skill with a release version finds only links with that version.
• The new check passes in just check.

by Opus-5.5 via Claude Code