Drive the README parity checks from one per-language table so the
Japanese README is held to the same contract as the English and Chinese
ones: switcher completeness, brand mark and demo placement, the animated
proof, share-card and real-repository proofs, the Hermes Agent and DSH
installation rows, and the Star History ending. check-release-identity
now validates the Japanese version badge, a Japanese-language
development/stable marker, and the Raven manual-ZIP boundary.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YPwjsicFpC7T1Enc5fPo5s
- release-source.mjs rejects non-exact-SemVer dshVersion and any
committed adapter scripts before packing or install
- distribution-acceptance.mjs verifies installed package name and
version against release.dshVersion before executing the entry
- pack.mjs runs npm pack with --ignore-scripts
- contract and staging tests cover prerelease acceptance, hostile
version rejection, and lifecycle-script rejection
Document hermes skills install and ship an optional directory plugin so Hermes can load the existing Node Skill without a Python renderer port.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat: add optional skill update awareness
Add the fail-silent, notification-only update checker and stable release contract, harden packaging and publication gates, keep the DSH 0.1.0 snapshot immutable, and fold in the reviewed codebase simplifications.
* test: accept platform-safe staging rejection
Linux can reject an ancestor swap while preflighting the leaf, while macOS detects the changed ancestor during snapshot validation. Both paths fail closed before staging, so assert the two exact safe outcomes instead of one platform-specific phase.
* test: guard staging swap hook against reentry
On Linux, recursive rm can re-enter the monkeypatched lstatSync before the swap flag was set. Fence the hook before mutating the fixture so the intended ancestor-swap attack runs exactly once.
Fix Windows tar and CLI resolution, validate the real pinned DSH runtime across Ubuntu, macOS, and Windows, and preserve JSON-only acceptance receipts. The integration remains explicit opt-in and isolated from non-DSH Archify paths.
Adds the explicitly installed @tt-a1i/archify-dsh Skill-only bundle with isolated packaging, cross-platform command handling, portable acceptance gates, and zero changes to the default non-DSH runtime.\n\nCloses #68.
杨嘉伟