Renewal Compass← Back to demo
Evidence and limitsRenewal Compass

Validation and release ledger

Software evidence

The repeatable software gate is locked Node 24 installation, lint, strict TypeScript, domain/storage tests, production build, dependency audit and production Playwright journeys. Exact final counts and observed outcomes are recorded after execution below. Browser evidence covers account categories, calculable packages, conditional review, cancellation, versioned history, withdrawal/revision, export, compatible refresh, invalid/unavailable/conflicting storage, raw-bound reset, keyboard/modal focus and revealed forms at 320, 390 and 1280×633. Every browser test rejects page errors, console errors and external application requests.

Proposed human validation — not performed

No human research has been conducted. Invite account leads and product managers in a separately authorized study to explain the distinction between obligation, need and request; explain the opportunity cost of the rejected custom package; and identify owner, conditions and exclusions before commitment. Observe errors and confidence, rather than assuming an automated pass proves comprehension. Candidate measures: correct category classification, explanation of shared roadmap impact, and identification of unresolved gates. No commercial lift, retention or endorsement is claimed.

Release evidence ledger

The first public release was independently verified on October 3, 2026: source commit 704a7b85f15ac7856ffa1f1a2a828f81469f61eb, successful verification and Pages release, clean local/public main agreement, and all 11 deployed files matching the local build and GitHub release artifact byte for byte. Pages was enabled before the first push. All 26 browser journeys also passed against the public URL, including failure, recovery, timing warnings and storage boundaries. A separate reviewer replay confirmed the blocked custom option, bridge recovery, exact conditional review and withdrawal with no browser errors.

Later documentation revisions retain the same application behavior and are verified by their own publication workflow. These are software/release observations. Personal product discussion and human comprehension are separate; no participant result is invented.

Observed local checks — October 3, 2026

Node 24.14.1 locked installation passed. Lint, strict TypeScript, runtime/tracked-file checks and production build passed. Domain/storage suite: 21 passed. Production Playwright suite: 26 passed after repairing the observed reverse-Tab modal wrap; export assertion was corrected to match the exact exclusion text. Audit: zero vulnerabilities. Production browser checks observed no page errors, console errors or external application requests.

Agent-browser production load/snapshot and screenshot inspection passed. Account brief, revealed desktop comparison, forms and modal layouts at 320, 390 and 1280×633 were inspected. Native modal focus is supplemented by explicit first/last button wrapping; Escape restores the initiating control. All seven product documents are included in the build and their local routes returned success.

The four workflow Action commit pins were resolved through GitHub's commit API: checkout 11bd71901bbe5b1630ceea73d27597364c9af683, setup-node 49933ea5288caeca8642d1e84afbd3f7d6820020, upload-pages-artifact 56afc609e74202658d3ffba0e8f6dda462b719fa, deploy-pages d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e. This verifies that the pinned commits exist; it is not deployment success.

Independent source review also identified ambiguous late review timing and unexplained disabled actions at the history limit. Both were repaired: dates after November 6 show a missed decision-deadline warning; dates on/after November 28 show a missed advance-renewal-window warning. The derived implication is retained in preview, immutable history and export. An incomplete date remains visibly unresolved. At 98 events, the visible notice explains that recording/withdrawal are paused and directs the user to export and deliberately reset. Three focused domain checks and two production journeys cover these boundaries; they are included in the 21/26 totals above, not added again.