worktree · HEAD@28e5280 → working-tree · GPT-6 (Codex)
Reviewers can now select overlapping annotations, collapse comments, keep semantic diff colors on hover, and synchronize split scrolling through settings. The npm package installs the agent skill without Git access. Verification records and deterministic quality reports distinguish author claims, current source, stale evidence and unavailable checks. The first scanner delivery supports ESLint and configured commands; optional adapters remain deferred.
npm testnpm run typechecknpm run lintnode tests/e2e/improvements.mjsnpm run test:uinpm run build -- --webpackAuthor confidence and passing claims are not measured accuracy. Records are unauthenticated; source hashes establish freshness, not who ran a command.
Recorded local checks; unauthenticated evidence. Baseline comparison unavailable. Static findings do not measure code accuracy.
node node_modules/eslint/bin/eslint.js . --format json --rule 'complexity: [warn, 15]' --rule 'max-depth: [warn, 4]'
.artifacts/whymark/b533372416ab4519fb5859a36dccd21c21933aa7da0362ccffb1bd7439e12ddc.log
SHA-256 b533372416ab4519fb5859a36dccd21c21933aa7da0362ccffb1bd7439e12ddc
npm run typecheck
.artifacts/whymark/0f80c6df94eee3539cd51fc9109c419630ed9af937aaac2b7f410006fc3cc98b.log
SHA-256 0f80c6df94eee3539cd51fc9109c419630ed9af937aaac2b7f410006fc3cc98b
36 of 36 findings shown
complexityFunction 'main' has a complexity of 22. Maximum allowed is 15.
src/cli/whymark.ts:115Rule documentationcomplexityFunction 'FilePanel' has a complexity of 30. Maximum allowed is 15.
src/components/whymark/file-panel.tsx:103Rule documentationcomplexityFunction 'UnifiedRow' has a complexity of 23. Maximum allowed is 15.
src/components/whymark/file-panel.tsx:639Rule documentationcomplexityFunction 'SplitRow' has a complexity of 33. Maximum allowed is 15.
src/components/whymark/file-panel.tsx:747Rule documentationcomplexityFunction 'toSplitRows' has a complexity of 22. Maximum allowed is 15.
src/components/whymark/file-panel.tsx:1058Rule documentationcomplexityFunction 'renderBlocks' has a complexity of 28. Maximum allowed is 15.
src/components/whymark/markdown.tsx:12Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/components/whymark/markdown.tsx:139Rule documentationcomplexityFunction 'NoteCard' has a complexity of 21. Maximum allowed is 15.
src/components/whymark/note-card.tsx:22Rule documentationcomplexityFunction 'ReviewView' has a complexity of 22. Maximum allowed is 15.
src/components/whymark/review-view.tsx:47Rule documentationcomplexityFunction 'readQuality' has a complexity of 22. Maximum allowed is 15.
src/lib/quality/import.ts:13Rule documentationcomplexityArrow function has a complexity of 27. Maximum allowed is 15.
src/lib/quality/import.ts:27Rule documentationcomplexityFunction 'parseESLint' has a complexity of 29. Maximum allowed is 15.
src/lib/quality/import.ts:43Rule documentationcomplexityAsync function 'scanQuality' has a complexity of 26. Maximum allowed is 15.
src/lib/quality/run.ts:55Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/quality/run.ts:72Rule documentationcomplexityFunction 'installSkill' has a complexity of 19. Maximum allowed is 15.
src/lib/skill/install.ts:15Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/evidence-node.ts:52Rule documentationcomplexityArrow function has a complexity of 30. Maximum allowed is 15.
src/lib/whymark/evidence.ts:39Rule documentationcomplexityFunction 'parseUnifiedDiff' has a complexity of 42. Maximum allowed is 15.
src/lib/whymark/git.ts:204Rule documentationcomplexityFunction 'parseWhymark' has a complexity of 29. Maximum allowed is 15.
src/lib/whymark/parse.ts:96Rule documentationcomplexityFunction 'parseFrontmatter' has a complexity of 37. Maximum allowed is 15.
src/lib/whymark/parse.ts:263Rule documentationcomplexityFunction 'parseNoteHeader' has a complexity of 31. Maximum allowed is 15.
src/lib/whymark/parse.ts:686Rule documentationcomplexityFunction 'setField' has a complexity of 31. Maximum allowed is 15.
src/lib/whymark/parse.ts:864Rule documentationcomplexityFunction 'parseVerifyClaim' has a complexity of 17. Maximum allowed is 15.
src/lib/whymark/parse.ts:1068Rule documentationcomplexityFunction 'serializeNote' has a complexity of 19. Maximum allowed is 15.
src/lib/whymark/serialize.ts:125Rule documentationcomplexityFunction 'collectSourceDiagnostics' has a complexity of 31. Maximum allowed is 15.
src/lib/whymark/validate-tree.ts:60Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:67Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:69Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:72Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:73Rule documentationmax-depthBlocks are nested too deeply (6). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:78Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:82Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:84Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:88Rule documentationmax-depthBlocks are nested too deeply (5). Maximum allowed is 4.
src/lib/whymark/validate-tree.ts:90Rule documentationcomplexityFunction 'validateDocument' has a complexity of 44. Maximum allowed is 15.
src/lib/whymark/validate.ts:31Rule documentationcomplexityFunction 'verifyDocument' has a complexity of 21. Maximum allowed is 15.
src/lib/whymark/verify.ts:63Rule documentationAgents need to author precise, source-backed notes without manufacturing confidence or coverage. The installed guidance must explain the new metadata and explicit execution boundary using resources shipped in the package.
$ npm testAgents need to author precise, source-backed notes without manufacturing confidence or coverage. The installed guidance must explain the new metadata and explicit execution boundary using resources shipped in the package.
$ npm testKeep the implementation and its acceptance criteria together so a later agent can continue the approved scope without reconstructing decisions.
Keep the implementation and its acceptance criteria together so a later agent can continue the approved scope without reconstructing decisions.
Keep the implementation and its acceptance criteria together so a later agent can continue the approved scope without reconstructing decisions.
The shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe shipped CLI must contain the same installer, format handling and evidence checks as the source, so npm consumers receive the tested behavior.
$ npm run build:cliThe CLI bundle is generated from already-linted TypeScript; linting its tree-shaken output reports unused generated imports rather than actionable source defects.
$ npm run lintUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testAgents need to author precise, source-backed notes without manufacturing confidence or coverage. The installed guidance must explain the new metadata and explicit execution boundary using resources shipped in the package.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testUrgency means action priority, not risk or measured correctness. Emit it as a body field because the baseline v1 reader preserves unknown fields but discards unknown header attributes; retain invalid/unknown evidence without interpreting it as success.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ npm run test:uiKeep the implementation and its acceptance criteria together so a later agent can continue the approved scope without reconstructing decisions.
Keep the implementation and its acceptance criteria together so a later agent can continue the approved scope without reconstructing decisions.
Deterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckOverlapping reasons must remain individually reachable without changing the meaning of added/deleted code. Independent disclosure and measured compact placement keep comment height from breaking the code reading flow.
$ node tests/e2e/improvements.mjsA passing author claim must not look like independently checked code. Present source freshness, imported provenance and concrete findings separately while keeping selection and keyboard navigation consistent.
$ npm run typecheckReviewers need synchronized comparison without losing the option to inspect each pane independently. Browser preferences are isolated from code decisions and continue working when storage is blocked.
$ node tests/e2e/improvements.mjsReviewers need synchronized comparison without losing the option to inspect each pane independently. Browser preferences are isolated from code decisions and continue working when storage is blocked.
$ node tests/e2e/improvements.mjsDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testReviewers need synchronized comparison without losing the option to inspect each pane independently. Browser preferences are isolated from code decisions and continue working when storage is blocked.
$ node tests/e2e/improvements.mjsUsers of the npm artifact cannot depend on access to the private source repository. Resolve bundled resources from the installed package, expose explicit installation and scan commands, and preserve existing CLI aliases and customized agent files.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ node tests/e2e/improvements.mjsRecorded claims can outlive the code or tests they describe. Bind execution results to normalized review/source/output identities, retain contradictions and unavailable states, and check local citations without executing or fetching imported content.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm testExercise observable behavior and failure boundaries rather than only matching implementation text: overlapping selection, reversible file decisions, evidence freshness, unsafe destinations and scanner cancellation must remain reliable.
$ npm testDeterministic diagnostics provide inspectable feedback without model judgment. Configured tools run in project context; unavailable scans and dirty or incompatible baselines cannot become a clean comparison, and superseded scans must not replace newer results.
$ npm test
Agents need to author precise, source-backed notes without manufacturing confidence or coverage. The installed guidance must explain the new metadata and explicit execution boundary using resources shipped in the package.
$ npm test