Skip to content

docs(audit): 2026-11-02 constitution-vs-reality audit — zero new drift - #670

Draft
rosscado wants to merge 2 commits into
mainfrom
docs/constitution-audit-2026-11
Draft

rosscado wants to merge 2 commits into
mainfrom
docs/constitution-audit-2026-11

Conversation

@rosscado

@rosscado rosscado commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Fourth run of the recurring audit chartered by #535 and doc/constitution-audit.md, fired by the monthly cloud routine (doc/scheduled-routines.md). Hermetic — no real-host harness run, no .env.production loaded.

Verdict

Zero new drift. Only one governance-relevant commit landed since the 2026-10-05 report (e7498a3, the #654 fix) — confirmed closed, and the fix re-verified live against the trigger's own config. #665 remains open and accurate, not re-filed. The awaiting-founder queue (#652, #617, #556, #554) is unchanged from October.

Lens (a) — governance docs vs reality: PASS

All standing grants/gates/claims in AGENTS.md re-verified against reality; see the report's table for the full list. Highlight: doc/scheduled-routines.md's tool-access claim, flagged as known drift in the last two reports (#654), is now accurate — re-confirmed against the live trigger config.

Lens (b) — Layer-3 harness health: PASS

  • npm ci, npm run e2e:build — clean.
  • npm test — green: 266 Vitest files, 3051 passed / 1 skipped; Jest + tsc --noEmit clean.
  • npm run test:e2e — blocked by a sandbox Chromium-revision mismatch (cache at 1243, pinned requirement 1223) — an environment gap, not repo drift, corroborated by 10 consecutive green e2e runs on main via the Actions API.
  • Spec-inventory guard: 5/5 passed, 22 specs, all documented in e2e/README.md.

Lens (c) — Layer-4 + ops tooling (static): PASS

Every harness script, subcommand, and target list matches its docs; release/ops tooling degrades cleanly without credentials, as documented. No real-host harness run.

Full report: doc/audit-reports/2026-11-02.md.



Generated by Claude Code

Fourth run under doc/constitution-audit.md (#535), third fired by the
monthly cloud routine. All three lenses pass against origin/main@e7498a3:

- Lens (a): every standing grant/gate/claim re-verified. Only one commit
  touched governance-relevant files since the October report (e7498a3,
  the #654 fix) — confirmed closed and the fix verified live against
  the trigger's own config. #665 (release:plan baseline-without-tags)
  remains open and accurate, not re-filed.
- Lens (b): npm ci, e2e:build, and full npm test (266 Vitest files,
  3051 passed/1 skipped; Jest green; tsc clean) all green locally. The
  full Playwright test:e2e run hit a sandbox Chromium-revision gap
  again (cache now at 1243, pinned requirement still 1223) — an
  environment gap, not repo drift, corroborated by 10 consecutive
  green e2e runs on main including the current HEAD. The spec-
  inventory guard passed 5/5.
- Lens (c): every harness script, subcommand, and target list matches
  its docs exactly; release/ops tooling degrades cleanly without
  credentials, as documented.

Verdict: zero new genuine drift. No issues filed. 4 issues (#652, #617,
#556, #554) remain correctly in-flight behind awaiting-founder,
unchanged from October.

Claude-Session: https://claude.ai/code/session_017G6UDaPR178FmAAZ9qwoqo

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@rosscado

rosscado commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

Independent review verdict: approve the content, no changes requested.

Re-derived the report's key claims against primary sources rather than trusting the write-up:

No factual errors found, no overclaiming, nothing that should have been filed as drift but wasn't. path-guard already green (docs-only PR, no gated paths touched). Clear to merge once test (22.x) and e2e finish green.


Generated by Claude Code

This PR's own required e2e check failed after the static audit work was
done and reviewed: GitHub's ubuntu-latest runner now resolves to Ubuntu
26.04, which the pinned @playwright/test@1.60.0 can't install Chromium
on. Diff-independent (confirmed on this docs-only PR), so it blocks the
required gate for every PR until fixed. Filed as #671, awaiting-founder
since the fix touches the founder-gated .github/workflows/e2e.yaml.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017G6UDaPR178FmAAZ9qwoqo
@rosscado

rosscado commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

The required e2e check (https://github.com/Pedal-Intelligence/saypi-userscript/actions/runs/41401514311) failed on this PR, but not because of this PR's diff (which only adds doc/audit-reports/2026-11-02.md). The "Install Playwright Chromium + OS deps" step fails in ~1s:

BEWARE: your OS is not officially supported by Playwright; installing dependencies for ubuntu26.04-x64 as a fallback.
Cannot install dependencies for ubuntu26.04-x64 with Playwright 1.60.0!
Failed to install browsers
Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64

GitHub's ubuntu-latest runner now resolves to Ubuntu 26.04, which the repo's pinned @playwright/test@^1.60.0 can't install Chromium on. This is diff-independent and will fail on every PR until fixed — test (22.x) and e2e-firefox are both unaffected (neither does a Playwright-Chromium browser install) and are green on this same run.

The fix (pin the e2e job's runner, or upgrade Playwright) touches .github/workflows/e2e.yaml, a founder-gated path per path-guard, so I can't push it from here. Filed as #671 (awaiting-founder) and folded into this run's own report as this cycle's one genuine drift item (the report in this PR now reflects it — see the Lens (b) addendum).

This PR itself stays as-is (zero new governance drift besides #671, already filed separately) and is not mergeable until #671 is resolved upstream, since it can't get a green required e2e run until then.


Generated by Claude Code

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants