Repository navigation
Skill Mesh v2.0.1
Skill Mesh v2.0.1
Patch release over v2.0.0. Qualified source: cbd6544db71f5d73d324e1da19791ac2c8ae5861.
What changed
Operator-facing documents are saved as files, never published as hosted Artifacts. The new single owner is _shared/document-output.md: a skill that produces a document the operator reads later writes one self-contained HTML file to docs/<skill-name>/ inside the project repository and reports the repository-relative path. This applies identically to the Claude, Codex, and GitHub Copilot profiles.
| Skill | Before v2.0.1 | v2.0.1 |
|---|---|---|
plan-redline |
Claude: private hosted Artifact (https://claude.ai/artifact/...) recorded as the Proposal: locator; Codex/Copilot: documentation/<plan-slug>-proposal.html |
All hosts: docs/plan-redline/<plan-slug>-proposal.html, recorded as the Proposal: locator |
repo-update Step 12 |
Claude: guided tour published with the Artifact tool; Codex: an unspecified file in the repository | All hosts: docs/repo-update/<project-slug>-<phase-or-version>.html, committed and pushed in its own docs: commit when Steps 9-10 ran; Tour: line carries the path |
- A plan whose
Proposal:line still records a hosted URL is migrated on the next/plan-redlinerun: the file is written, the line is replaced with the path, and the report states that the prior hosted copy remains published and is now stale. A recordeddocumentation/...-proposal.htmlpath is kept as the republish target unless the operator asks for a move. --local-onlyonplan-redline(passed byplan-expedite) is now a compatibility no-op.- The
artifact-designskill is still loaded on Claude Code for page craft; it no longer decides location. - Provider guides, parity deltas, workflow diagrams (
plan-redline,repo-update), and the routing chart were updated to match. A new package-integrity test (tests/package-integrity/test_document_output_contract.py) pins the contract on every provider.
No skill was added or removed: 57 Claude skills, 54 each for Codex and Copilot. Other skills that write Markdown reports or run evidence under their own existing defaults (judge-ui, judge-motion, tier-escalate, tier-offload, skill-iterate, skill-evolve, user-brainstorm) are unchanged in this patch; they never used the Artifact tool.
Installation and upgrade
Same procedure as v2.0.0. Use Windows PowerShell 5.1, verify the archive against the attached .sha256, extract to a dedicated directory, and run the installer against the existing home:
powershell -NoProfile -File tools/install-skill-mesh.ps1 -Provider claude -Home C:\path\to\consumer-home -DistDir .\distUse -Provider codex or -Provider gpt for the other hosts. Retain the v2.0.0 distribution and back up the discovery tree and .skill-mesh-install.json before upgrading. Start a fresh host session after installation.
Qualification
Qualification on the qualified source: pytest over tests/package-integrity, tests/distributions, tests/release, tests/router and tests/smoke -- 1453 passed, 1 skipped (4h41m). tools/release.ps1 -Provider all then rebuilt the distributions into a clean stage and re-ran the package-integrity gate against the staged artifacts before writing CHECKSUMS.txt (440 dist files). The full repository-root suite (calibration, experiments, production-toolchain, telemetry) was not re-run for this patch; it last ran green at v2.0.0.
The v2.0.0 known limitations are unchanged.