[yyods]

Summary

• Consolidate the exact published firmware v0.6.1 source (c8f549e), measured baseline, maintained specifications/tests, and reviewed App BLE lifecycle corrections.
• Retain App 0.2.0 build-8 offline privacy and Google Play handoff work.
• Bring the published learning screenshots, features/functional diagram, and all current website guidance into main with its existing dependency-security updates.
• Preserve the engineering chronology and owner-confirmed publication record without relabeling incomplete automated HIL.
• Fix pre-PR website formatting and the frozen protocol snapshot's missing contributor-guidelines link target without changing the protocol bytes.

Verification before PR

• Flutter analysis and Dart formatting: clean; non-golden tests: 894 passed; pixel-golden tests: 31 passed.
• Full website check: 342 tests, formatting/lint/types, zero-vulnerability audit, dependency notices, compatibility check, and both static/Sites builds passed.
• Publication tests: 41 passed; Markdown link gate passed.
• Source-policy and PR-range DCO checks passed.
• Fresh firmware shell/conformance run: all 77 test files passed, zero failures (host-only; no boards operated).
• Published board runtime, native modules, overlays and version pins match source c8f549e. The CI follow-up changes host evidence writers/tests only; prior full host and reproducible five-profile build evidence is retained.

Scope and cleanup

This consolidates accumulated local platform work, not only the last homepage edit. Conflicting source histories were resolved to the exact published firmware and current deployed website. Private, unfinished qualification experiments were archived instead of merged.

All 18 local auxiliary worktrees, dirty files, ignored owner backups, branch tips and Git metadata were preserved recoverably before removing their registrations and 27 obsolete local branch names. Only the primary worktree and local main/integration branches remain. The two old remote docs branch histories are reachable through this PR branch before their names are removed.

No board operations, new firmware build, store upload or website deployment occurred in this Git workflow. Publication relies on the owner's explicit qualification confirmation; original incomplete automated evidence remains unchanged. This PR does not bypass CI or branch protection.

Integration details: docs/testing/platform-integration-2026-09-11.md.

CI correction and README follow-up

Both original firmware-host jobs failed the same replacement-file preservation test. Keeping the original evidence-file descriptor open through validation and rollback prevents Linux inode reuse from causing deletion of a replacement. Both affected host writers are fixed, without relaxing release gates or changing firmware binaries.

• New deterministic regressions demonstrate the original failure on macOS as well as checking the Linux-sensitive lifetime invariant.
• Affected writer/gate suite: 80 passed under Python 3.12.
• Publication tests: 42 passed; Markdown links and six roadmap guards passed.
• Website tests: 342 passed.
• README and public roadmap now identify v0.6.1, exact release evidence, official examples/branch selection, tutorials/diagram, App source version and store-availability boundaries.
• Full host rerun and fresh GitHub CI remain separate checks; no hardware testing was restarted.

Related to #24, but does not auto-close it: this PR records the owner's completed-qualification confirmation and publication, not completion of every original collector-generated evidence requirement. Explicit closure as superseded would be a separate maintainer decision.

Details: docs/testing/pr32-ci-remediation-2026-09-11.md.

Final validation update for 9408778

• Full local Python 3.12 host/release suite: 1,950 tests, zero failures, 19 skips, completed in 1,124.949 seconds.
• The previously failing Ubuntu firmware-host check now passes in PR run 34621337759.
• Website, documentation, App, golden and initial source-policy jobs have passed. Remaining firmware-build/Android jobs were still running when this update was recorded; no complete-workflow or merge claim is made.
• Updated README release/recovery/tutorial/diagram/source/example links returned HTTP 200; the public v0.6.1 release metadata still matches its recorded SHA-256.

[yyods]

Merge blocker resolved without changing files

The branch was green and conflict-free, but main permits only rebase merges.
PR #32 contained 299 commits and two merge commits, and GitHub returned
This branch can't be rebased. GitHub's documented rebase-merge limit is
100 commits.

The complete reviewed history is preserved under
archive/pr32-reviewed-9408778,
including the original specification/red/green commits and published firmware
source c8f549e.

This PR now has one DCO-signed commit parented on current main. The complete
Git tree is unchanged: bf864f70c234085b0607cd8c1a8948020bcac0a1 before and after.
No source, documentation, asset, dependency pin, submodule pin or firmware byte
was changed by this history repair. An exact-head force lease protected the
branch update.

All repository protections remain unchanged. Required CI is rerunning on the
new commit before an ordinary rebase merge; no administrator bypass or
manufactured check result is being used. Issue #24 remains a separate decision.