Maneek21/Deft

Current state Refreshed September 24, 2026 against master at 1427f66. The production browser smoke and individual keyboard improvements do not establish end-to-end keyboard or screen-reader coverage. No core-path screen-reader certification was found in this review. Evidence: browser smoke, roadmap. Remaining work Certify login, primary navigation, task creation, a governed agent approval, and personal MCP connection setup/revocation. Use the navigation and identity model of the tested revision. Acceptance evidence Complete each flow using only the keyboard; record revision, browser, and viewport. Verify visible focus, logical tab order, semantic names/labels, and useful validation feedback. Verify focus enters dialogs appropriately, remains contained where required, and returns sensibly on close. Record a manual screen-reader pass with a named reader/browser pair, covering controls, errors, and completion feedback. Add stable automated regression checks for discovered failures;

Current state Refreshed September 24, 2026 against master at 1427f66. The public-docs checker already includes README.md, validates local Markdown links (including current image syntax), and reports missing targets. CI runs it through pnpm docs:check. The remaining gap is a regression fixture, not a new checker. Evidence: checker, CI; delivered through #330. Remaining work and acceptance evidence Validate current local README image paths and clearly report a missing target. Run the checker in documentation CI. A disposable fixture with an existing local image passes. A missing or renamed local image fails with a nonzero exit and identifies the README and missing path. The regression coverage runs in the documentation CI path. Record the focused test command and result in the fixing PR. Scope File existence only. Detecting whether screenshots match the current UI is separate work. Do not overwrite or remove repository screenshots to construct a failing fixture. Ownership and pri

Current state Refreshed September 24, 2026 against master at 1427f66. The 60-person harness already emits JSON/HTML reports and enforces configured write/read latency, queue-drain, recovery, and attention-projection budgets. It is exposed as pnpm certify:60-person. No recurring workflow invoking that harness was found. Remaining work and acceptance evidence Wire the existing harness into weekly and manually dispatched CI, reusing its budgets and verdict. Run weekly on the default branch and support manual dispatch. Use disposable test data and infrastructure; preserve cleanup on failure. Record the exact commit, workload, configured budgets, result, and execution environment. Upload machine-readable results and a compact job summary, including failure diagnostics when available. Set explicit artifact retention and workflow timeout/concurrency limits. A failed verdict fails the job; missing results cannot appear as a pass. Demonstrate one successful workflow run and verify the f

Current state Refreshed September 24, 2026 against master at 1427f66. Official release builds and release manifests still target linux/amd64. ARM64 is new supported-platform work, not a completed feature or a regression. Evidence: release workflow, manifest generator, limitations. Remaining work and acceptance evidence When ARM64 demand and an implementation owner are established, publish and certify an ARM64 release path. Publish a multi-architecture image or a documented separate linux/arm64 image. Run installation, doctor, and browser smoke on ARM64 hardware or clearly identified emulation. Record tested platform/environment and exact image identity. Keep signatures, provenance, manifests, and operator instructions accurate for every supported image. Verify the existing amd64 path remains functional. Ownership and priority Unassigned; Later. Excluded from Next preview hardening. Revisit when a concrete ARM64 installation need and a maintainer are identified; no delivery date