chore(release): 0.7.0

[modusensus]

Version bump to 0.7.0 across the four manifests, plus one false statement removed from the release notes template.

What ships in 0.7.0 (since v0.6.0)

PR	What it was
#25	test/docs-pair.test.js — every docs/ translation pair held to structure and identifiers, with the shared Markdown scanner pinned by seven crafted documents
#26	host facts re-measured against the installed harness 0.1.6-alpha.1 by driving the real skill provider, plus tools/probe-skill-roots.mjs left as the re-measurement path
#27	the rustls case study — the project's first TRUE POSITIVE, with a bidirectional PoC as gate-4 evidence
#28	euthyna audit now declares when the manifest it measured is not the one at --head
#29	the repository-root-only manifest boundary recorded as a known limit, and three stale counts corrected

The bump itself

package.json, .claude-plugin/marketplace.json (metadata.version), .claude-plugin/plugin.json, plugin.yaml. test/manifest-version.test.js pins all four against package.json — it exists because 0.5.0 shipped them a release behind and nothing compared them.

The template sentence

.github/release-notes-template.md said:

The CLI's report text is currently Chinese; the audit discipline (the skill) is host-agnostic Markdown.

That stopped being true when bilingual output landed, and test/i18n.test.js pins --lang en producing English report text. Both skill editions are in the package (package.json files lists .agents/skills/euthyna/ and .agents/skills/euthyna-en/). Because the workflow substitutes {{version}} into a fixed template, every release repeats this sentence verbatim — so it corrected the claim rather than shipping it one more time.

Verified

node --test                       → tests 246 / pass 245 / fail 0 / skipped 1
sed -e "s/{{version}}/0.7.0/g"    → "## euthyna 0.7.0",  install line euthyna@0.7.0
npm pack --dry-run                → version: 0.7.0, total files: 38,
                                    shasum 11781b18550715ab4ed0c65cd1333fdf2097c045

The skipped test is the deliberate one: every exploit expectation holds reports itself skipped wherever tar is not bsdtar (this shell resolves Git Bash's GNU tar first). CI's Windows runner runs it in full.

What is deliberately not in this PR

• No changelog section in the release notes. The fixed-format template is a design choice (AGENTS.md: "every release carries one fixed format, and format changes are reviewed like any other file"); adding per-release highlights is a template redesign, not a bump.
• No tag yet. After this merges: CLAWHUB_TOKEN must be re-created in the repository's web-UI secrets (publish.yml's preflight exits 1 on an empty value — that is intentional, it is the fix for the silent skip that let the ClawHub listing sit three releases behind), then the workflow_dispatch rehearsal renders the notes without publishing, and only then v0.7.0 is pushed.
• The AGENTS.md release record for 0.7.0 will be added from the measured run, the same way 0.6.0's was.

Summary by Sourcery

Prepare the repository for the 0.7.0 release by synchronizing package versions and correcting the release notes language-support statement.

Enhancements:

• Update the project release metadata to version 0.7.0 across all supported manifests.
• Correct the release notes template to accurately describe bilingual CLI reports and mirrored Chinese and English skill editions.

[sourcery-ai]

Sorry @modusensus, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 days and 2 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only change bumps the project to 0.7.0 in all four manifests and updates the fixed release-notes template so its language and packaging claims reflect the current bilingual CLI and skill editions.

File-Level Changes

Change	Details	Files
Synchronize the release version across all package and plugin manifests.	Bump the package version to 0.7.0. Update marketplace metadata, plugin metadata, and YAML manifest versions. Rely on the existing manifest-version test to verify consistency with package.json.	package.json .claude-plugin/marketplace.json .claude-plugin/plugin.json plugin.yaml
Correct the release template’s language-support statement to match the bilingual CLI and packaged skill editions.	Document Chinese as the default and English via --lang en or EUTHYNA_LANG=en. State that both mirrored Chinese and English skill editions are published.	.github/release-notes-template.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[modusensus]

@sourcery-ai review

[sourcery-ai]

Sorry @modusensus, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 5 days and 2 hours by commenting @sourcery-ai review. Upgrade to get a review now.