Five lenses filed 20; 8 survived verification.
**release.yml would have failed on the first tag.** The `announce` job called
the ops reusable with no `with:` block, but that reusable resolves
TAG="${INPUT_TAG:-$EVENT_TAG}" where EVENT_TAG is github.event.release.tag_name
-- empty, because this workflow is triggered by `on: push: tags`, not
`on: release`. The job would have exited 1 on "No release tag available" for
every release. Filed independently by three lenses and confirmed against the
reusable's actual source; docs/12 §2.3 had the same omission and is fixed too.
Ironically the comment right above it explains why the workflow deliberately is
not event-driven -- which is exactly what makes tag_override mandatory.
**Nothing checked the BUILT manifest.** The unit test reads wxt.config.ts,
which proves what we ask for, not what WXT emits. Those differ: a dev build of
this same config carries ["bookmarks","storage","tabs","scripting"] and
host_permissions ["http://localhost/*"]. Production is clean, but that is
WXT's behaviour, not ours. scripts/check-manifest.mjs now gates the artifact
and runs in both CI and release; verified by editing a built manifest. The
README sentence claiming a test asserted the built manifest was false and is
corrected -- the same overclaim I had already made once verbally.
**The contrast test I added last commit could not see its own bypass.**
TabBar's `.locked { opacity: 0.65 }` composites --fg-muted against the page and
drops the label to 2.83:1. The test reads token values, so alpha applied on top
is invisible to it. Opacity removed; the padlock and title already carried the
signal. TEXT_PAIRS also widened to check the status colours on --bg, not only
--bg-raised.
**docs/09 T3 was signed off with half its mitigation unbuilt.** The row has
always specified a ⚠ badge for dangerous schemes; only the blocking existed. A
`javascript:` bookmark titled "Your bank" rendered identically to a safe one
and its Open button silently did nothing. isBlockedUrl now drives a badge, and
a refused open raises a toast.
Also: the five row action buttons had glyphs as their accessible names (content
beats title in accname), so voice control could not address them; the manifest
test's literal-harvesting regex would have passed a spread or identifier;
resolveNewFolderParent returned a focused unmodifiable folder's id, which every
create rejects; and clipboard.ts was the only new module with no test.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
75 lines
2.5 KiB
JavaScript
75 lines
2.5 KiB
JavaScript
/**
|
|
* Assert the BUILT manifest — CLAUDE.md hard rule 1, docs/08 §2.
|
|
*
|
|
* The unit test in `tests/unit/manifest.test.ts` reads `wxt.config.ts`, which
|
|
* proves what we ASKED for. It cannot prove what WXT emitted. Those differ:
|
|
* a dev build of this exact config produces
|
|
* "permissions": ["bookmarks","storage","tabs","scripting"]
|
|
* "host_permissions": ["http://localhost/*"]
|
|
* because WXT injects them for its dev server. Production is clean today, but
|
|
* that is a property of WXT's dev/prod branch, not of anything this repo
|
|
* enforces — so the shipped artifact needs its own gate.
|
|
*
|
|
* Run after `npm run build` (or `npm run zip`). Zero dependencies, Node stdlib.
|
|
*/
|
|
import { readFileSync } from 'node:fs';
|
|
import { join } from 'node:path';
|
|
|
|
const MANIFEST = join(process.cwd(), '.output', 'chrome-mv3', 'manifest.json');
|
|
|
|
/** Exactly this, in any order. Adding one is a minor-version event (docs/09 §4). */
|
|
const ALLOWED_PERMISSIONS = ['bookmarks', 'storage'];
|
|
|
|
/** Keys that would widen the extension's reach. None may be present. */
|
|
const FORBIDDEN_KEYS = [
|
|
'host_permissions',
|
|
'optional_permissions',
|
|
'optional_host_permissions',
|
|
'content_scripts',
|
|
'background',
|
|
'web_accessible_resources',
|
|
'externally_connectable',
|
|
'declarative_net_request',
|
|
'devtools_page',
|
|
'chrome_url_overrides',
|
|
];
|
|
|
|
let manifest;
|
|
try {
|
|
manifest = JSON.parse(readFileSync(MANIFEST, 'utf8'));
|
|
} catch (cause) {
|
|
console.error(`check-manifest: cannot read ${MANIFEST} — run \`npm run build\` first.`);
|
|
console.error(` ${cause.message}`);
|
|
process.exit(1);
|
|
}
|
|
|
|
const problems = [];
|
|
|
|
if (manifest.manifest_version !== 3) {
|
|
problems.push(`manifest_version is ${manifest.manifest_version}, expected 3`);
|
|
}
|
|
|
|
const permissions = [...(manifest.permissions ?? [])].sort();
|
|
if (permissions.join(',') !== [...ALLOWED_PERMISSIONS].sort().join(',')) {
|
|
problems.push(
|
|
`permissions are ${JSON.stringify(manifest.permissions)}, expected ${JSON.stringify(ALLOWED_PERMISSIONS)}`,
|
|
);
|
|
}
|
|
|
|
for (const key of FORBIDDEN_KEYS) {
|
|
if (key in manifest) problems.push(`declares "${key}": ${JSON.stringify(manifest[key])}`);
|
|
}
|
|
|
|
if (problems.length > 0) {
|
|
for (const problem of problems) {
|
|
console.error(`::error::check-manifest: ${problem}`);
|
|
console.error(` ${problem}`);
|
|
}
|
|
console.error('\nSee CLAUDE.md hard rule 1 and docs/09 §4 before changing this.');
|
|
process.exit(1);
|
|
}
|
|
|
|
console.warn(
|
|
`check-manifest: clean — MV3, permissions ${JSON.stringify(manifest.permissions)}, no reach-widening keys.`,
|
|
);
|