fix(hello-status): match the registration to the manifest and gate drift in CI

[hamidfzm]

Problem

Release official plugins run 31945013113 failed on main:

Error: com.glyph.hello-status: manifest.json version 1.1.0 != plugin.json version 1.0.0

#6 bumped manifest.json to 1.1.0 so the sample plugin would be repackaged with its sandbox: false line, but left plugin.json at 1.0.0. scripts/release-official.mjs requires the two to agree before it packages anything, and nothing checked that pairing at PR time, so the mismatch could only surface in the post-merge release job, which no re-run can turn green.

Two related drifts came out of the same read:

• com.glyph.hello-status/plugin.json omitted sandbox, so the marketplace, which reads the registration for the consent prompt shown before the download, offered the ordinary install warning for a full-trust plugin. The installed manifest still triggers the full-access warning afterwards, so nothing ran unapproved, but users saw the wrong prompt first.
• com.glyph.dictionary-fa/manifest.json declares sandbox: false it does not need. It only calls ctx.assets.readText and ctx.spellcheck.registerDictionary, both implemented in the sandbox worker, and its published 1.0.0 package already runs sandboxed.

Changes

• plugins/com.glyph.hello-status/plugin.json: version 1.1.0 and sandbox: false, matching the manifest. packageUrl and sha256 are left alone; the release job rewrites them after merge.
• plugins/com.glyph.dictionary-fa/manifest.json: drop sandbox: false (least privilege, and it matches the released package). No version bump, so no re-release.
• scripts/check-plugins.mjs (new): the parity rules in one place, checking id against the folder name, version, apiVersion, sandbox (absent means sandboxed on both sides), and that every manifest-declared file exists. validate.yml runs it on every PR and release-official.mjs imports it, so the PR gate and the release gate read one source of truth. The id check moves out of the validate.yml shell loop into the script.
• scripts/build-index.mjs: the catalog badge names the trust mode either way. It only rendered "sandboxed" for an explicit sandbox: true, which nobody writes because it is the default, so the opt-out the badge exists to flag never showed up. Hello Status now reads official · full trust · no permissions.
• .github/workflows/smoke.yml (new): CI-time smoke tests, mirroring the split in the main Glyph repo between ci-smoke.yml (drive the real script) and the data checks.

Tests

scripts/release-official.test.mjs runs the real release script end to end against a throwaway repo whose gh is a shell stub, so packaging happens for real and nothing can reach GitHub:

• packages the plugin, creates the release, and rewrites packageUrl and sha256 (zip contents and digest asserted against the file on disk)
• fails on a version mismatch without releasing (the failure above, as a regression test)
• fails when the manifest declares a missing file
• skips a version already released on the remote, and one already tagged locally, without calling gh
• ignores community registrations

scripts/check-plugins.test.mjs unit-tests the parity rules, including that checkAll finds no problems in this repo.

Both run with node --test: no dependencies, no test framework. The smoke suite is POSIX only (shell stub plus Info-ZIP zip) and skips on Windows. The Smoke job on this PR runs all 16 tests, the 6 smoke cases included. Reverting the plugin.json fix and rerunning node scripts/check-plugins.mjs reproduces the exact CI error, this time at PR time.

Notes

index.json, index/tools.json, and docs/plugin-catalog.md are regenerated here, as the generator check on main now requires. After merge, main releases com.glyph.hello-status-v1.1.0 and rewrites packageUrl and sha256 in its own bot commit.