Repository navigation
Complete final release evidence, launch, operating handoff, and acceptance closure #75
Description
Original request
Relevant excerpt, lightly grammar-corrected for publication. Credentials, personal data, private paths, and unrelated transcript content are omitted.
Generate a final report covering the entire project and what real interaction with the PC host and board found in each area.
Source: session origin-main, authored turn 82.
Parent epic: #13
Requirement
Complete final release evidence, launch, operating handoff, and acceptance closure
Acceptance criteria
- Rebuild firmware/host from current source, record source/artifact hashes, upload/verify through the canonical host path, and authenticate HELLO.
- Run automated, simulator, and screenshot-driven interaction checks across every TUI page, keyboard/mouse control, settings editor, console completion, CLI, public library API, IPC/RPC, REST/WebSocket bridge, reconnect, programming, backup, and restore surface.
- Capture the packaged embedded WebUI at desktop and narrow widths in English/Persian, RTL/LTR, light/dark, keyboard-only and reduced-motion modes; verify dialogs, graphs, structured data, disconnect/reconnect truth, two-tab synchronization, command/event duplex, and zero console/network errors.
- Exercise every load-safe board path: identity/settings/menu queries, front-panel preview and remote keys, measurements, displays/audio, door/BT events, illumination/PWM/RGB, RF, macro timing/cancel, and safe output reset; record relay/motion/LCD/load checks as passed, failed, or explicitly human-blocked rather than assuming them.
- Launch the final canonical host against the board and verify secondary IPC operation.
- Provide complete board/host operating, safety, programming, backup, recovery, and troubleshooting instructions.
- Publish a final per-area verification matrix with exact commands, artifact hashes, firmware identity, screenshots/logs, observed results, remaining blockers, and restored safe output state.
- For every remaining human-assisted item, first back up settings, force safe outputs, confirm COM ownership, and prepare the exact capture; then show WAIT and play the unique continuous attention ringtone, stopping it promptly after the response and never overriding Do Not Disturb/Silent.
- On final successful launch and handoff, leave the board in a safe-output state with the seven-segment display showing ok.
- Do not call an ad-hoc development completion a nightly firmware; publish the exact release-channel description plus host source/artifact identity and firmware/EEPROM identity.
- Treat bridge-owned Go replacement, AVR flashing, EEPROM provisioning/restore, readback verification, rollback evidence, and live board behavior as mandatory closure gates rather than substituting source or VirtualBoard success.
- Close parent epics only after every linked child has current completion evidence.
Current evidence and gaps
A prior host was launched and a current firmware image was verified, but source/tooling has continued to change and the outstanding physical/UX/network/finalization checks prevent release closure.
Traceability
- Canonical checklist section: Final hardware validation and handoff
- Includes only curated, issue-relevant prompt excerpts; complete transcripts, credentials, secrets, and private paths remain unpublished.
Activity
atomicdeploy commentedon Aug 12, 2026
Release status: PR #180 was merged as explicitly authorized WIP, and PR #132 auto-merge is blocked by CI compile failure. No LED WIP is approved for runtime deployment, packaging release, or physical flash. Final release acceptance must include the AVR-first/same-source gate, later VirtualBoard parity, canonical package identity, bridge-only flash, EEPROM backup/restore, and live rendered-frame/owner verification.
atomicdeploy commentedon Aug 13, 2026
Launch handoff checkpoint: protected-main 9875397 is running at cafe-pc.local:8787 from the exact 101-file CI package; board 37D3BC5C is connected on COM4 after guarded Urclock flash; auth, IPC/HTTP/WS/Socket.IO, PWA, UPnP/SOAP, and live telemetry passed. Browser is left on Settings for token entry. Remaining launch gates are the physical close/reopen event, TM1637 responsiveness observation, prepared hardware tests, reciprocal David-PC discovery, COM owner access, and CPU churn, linked from #183.
atomicdeploy commentedon Aug 23, 2026
Current delivery handoff is consolidated at #68 (latest checkpoint comment) and the durable chronology is now in
docs/Alpha-Delivery-Ledger.md. #284 is merged; #287 is the only active near-term dependency repair. Drafts #274/#275/#272 remain explicitly blocked and ordered. Hardware acceptance epics #69–#74 and release closure here remain open until physical evidence is collected.atomicdeploy commentedon Sep 10, 2026
Final integration lane 2026-09-11: merge the frozen tested action/progress (#303), macro (#304), and peer-update (#305) checkpoints with the bounded Windows owner-helper fix, regenerate shared contracts/assets, and run one exact integrated package gate. Preserve normal merge ancestry and supersede originals only after the combined branch is merged. User requests operational host/Web/board delivery, not source-only completion. Current UART programming attempt refused all writes because COM ownership remained busy; normal operation recovery is separately in progress. Full MCU/physical macro acceptance remains #44/#74.
atomicdeploy commentedon Sep 10, 2026
Live delivery regression / lane claim: an already-open Web client reconnects to the replaced host but retains its previous app/lazy-chunk bundle; navigating an unloaded page then requests a removed hash and fails. Source currently checks resource mismatch only at initial startup and explicit completion events, not ordinary socket reconnect after an external install/restart. Bounded corrective lane agent/client-reconnect-resources-sep11 will check fresh host UI/build identity on every transport open, reload once on mismatch using the existing loop guard/storage fallback, and cancel stale-generation checks. Acceptance: simulated external host replacement updates an existing client without manual refresh; matching identity does not reload; disconnect/stop/out-of-order responses cannot reload a superseded session. No board or host restart in this lane. Related packaging contract #64.
atomicdeploy commentedon Sep 10, 2026
Reconnect upgrade fix is implemented in #310, source checkpoint 294e6e1. Full local Web verification now passes: 40 files / 230 tests, including the external replacement-without-updater-event regression; TypeScript and repository checks pass. Matching identities remain open; old-generation/disposed requests cannot trigger reload; endpoint checks are bounded with one retry. Tracked bundle regeneration and canonical CI packaging are underway. This is source/test evidence, not a claim that a pre-fix already-loaded browser magically gains new code: that first rollout still requires the existing update-completion reload path or one controlled reload. New-client reconnect acceptance against a subsequent installed build remains the deployment coordinator test.
atomicdeploy commentedon Sep 10, 2026
Delivery checkpoint: #307 merged (including #303-306, preserving #274/#275); stale #272 closed with remaining peer acceptance linked. #309 native watcher race is also merged. Canonical Windows CI644 is installed, healthy and running with verified EXE icon/version, current embedded Web, UPX and C ABI; canonical source/bin contains the same package. Live board is connected/out of Prog with original settings restored, silent OFF and illumination Auto; firmware remains the prior build because guarded UART attempts wrote nothing. Named macro CLI + Web recording/save/library/playback are operational and share live state. Tests exercised display and relays-already-off only; loaded motion is not claimed. Timing successes:15.733ms and78.715ms max; negative startup-latency evidence remains in #44. #310 fixes the reproduced stale-browser bundle after external host replacement. #308 development-upload backup policy is under final regression repair; advanced known-good reuse/promotion remains #216. Full remaining handoff is docs/September-Delivery-Checkpoint.md plus canonical backlog; do not equate merged source with unperformed hardware acceptance.
atomicdeploy commentedon Sep 10, 2026
Final #310 source is 903a2c4, reconciled with merged #309 on main d17bd87. Web source, five new bounded-reconnect regression tests, documentation, and regenerated tracked assets are all pushed; local worktree is clean. Full Web 230/230, TypeScript, Vite, repository checker, and diff whitespace checks pass. The PR is Ready; canonical CI packaging and subsequent live client-reconnect verification remain the delivery lane. No hardware or running host was modified in this fix lane.
atomicdeploy commentedon Sep 10, 2026
Priority delivery update: PR310 is merged. Canonical Windows CI653 is installed and running healthy, with verified icon/version resources, current embedded Web, UPX integrity and C ABI. Original board firmware remains connected and operational, out of Prog, with operator-selected silent-off and illumination Auto preserved. The pre-fix browser needed one controlled reload; it now runs the reconnect-aware bundle. Final acceptance will replace this host with the integrated PR311 package and verify automatic client update. CLI-started playback/cancel-keep also propagated playing then cancelled at2/3 into the existing Web client without refresh. PR311 integrates the first-ACK timing correction, PR308 policy and public checkpoint evidence. No further firmware flash attempts or broader backup-history changes are being made in this focused pass.
atomicdeploy commentedon Sep 11, 2026
Delivered canonical Windows CI658 (source8ebb5766/package40a5daa9) with icons/version resources, current Web, tested UPX and C ABI. Installer reports healthy/data preserved. Two already-open clients automatically changed from the CI653 bundle to the CI658 bundle after external host replacement: no manual reload during this test. Both reconnected; lazy Device/workbench navigation loaded without JavaScript errors. Current board remains communicating on existing firmware, out of Prog, silent-off/illumination Auto preserved. Macro CLI and Web playback passed the100ms alpha target on the tested harmless definition. UART firmware upgrade is still blocked by bootloader handshake and is not claimed delivered. PR311 includes308/310 plus public checkpoint by normal ancestry; keep precise hardware/peer acceptance and remaining UI/backlog items open.