Skip to content

Validate optional LCD, USB lifecycle, and a harmless cancellable macro end to end #74

Open

Description

@atomicdeploy

Original request

Relevant excerpt, lightly grammar-corrected for publication. Credentials, personal data, private paths, and unrelated transcript content are omitted.

Complete real-board verification for the remaining LCD, USB lifecycle, macro, and safe interaction paths, explicitly recording any human-blocked checks.

Source: session origin-main, authored turn 82.

Parent epic: #13

Requirement

Validate optional LCD, USB lifecycle, and a harmless cancellable macro end to end

Acceptance criteria

  • With a backpack connected, verify 0x27/0x3F detection, both LCD rows, host text, and concurrent TM1637.
  • Unplug/replug USB and verify lifecycle events, authenticated reconnect, both DTR modes, TUI, and IPC updates.
  • Run and cancel a harmless named macro that labels TM1637, writes LCD text, changes one PWM channel, and toggles one general relay.
  • Capture logs/screenshots and restore all outputs to a safe state.
  • Use WAIT/ringtone only when the prepared pass reaches a real cable, LCD, or physical-observation step; stop it as soon as the user responds.

Current evidence and gaps

Each path exists in source or tests, but no current physical end-to-end pass covers the connected LCD, USB reappearance, and macro cancellation together.

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

  1. added
    🖥️ hostPC host, CLI, TUI, or library
    🧪 testingAutomated, simulated, UX, or hardware verification
    🔍 needs-hardwareRequires physical-board observation or operation
    on Aug 1, 2026
  2. atomicdeploy commented on Aug 9, 2026

    @atomicdeploy
    OwnerAuthor

    Live macro acceptance mapping

    This issue owns the first harmless, silent real-board acceptance of #44: record from host and board sources, preserve exact MCU timing deltas through streamed chunks/circular-buffer refill, list/name/category, cancel safely, and replay only non-actuating/non-audio commands until the human gate is satisfied.

    Motion/MOSFET/buzzer actions can share the canonical opcode path in software tests, but live actuator/audio execution remains gated by #69/#72 and strict silent mode. The board is not currently enumerated; no hardware action was attempted.

  3. atomicdeploy commented on Aug 12, 2026

    @atomicdeploy
    OwnerAuthor

    2026-08-12 reconciliation: integrated physical macro/USB pass

    This is the remaining integrated acceptance gate for the current task: verify optional LCD text and concurrent TM1637, perform USB/COM18 reconnect with native UART/Urboot, then run and cancel a harmless named macro. Record the host event stream and confirm all outputs return safe. Source-level capability is not sufficient for closure.

  4. atomicdeploy commented on Sep 11, 2026

    @atomicdeploy
    OwnerAuthor

    Live error investigation on CI670: the Web activity stream reported HOST-controlled LCD not detected at 0x27 or 0x3F. Go command i2c lcd status reports enabled=true, owner=PC, physical=false, address=0x00 (a subsequent attempt retained context deadline exceeded). Bounded, zero-data Go command probes i2c transfer 0x27 0 0 and i2c transfer 0x3F 0 0 both returned address NACK, in approximately 183.8 ms and 66.9 ms end-to-end HTTP time. This proves the responding board did not get an acknowledgement at those addresses; it does not prove whether the module is disconnected, unpowered, miswired or configured at another address. Physical LCD/backpack/address verification remains necessary. No arbitrary write, blind initialization, changed setting, or error suppression was used. Read-only follow-up and optional-peripheral error policy remain tracked here.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔍 needs-hardwareRequires physical-board observation or operation🖥️ hostPC host, CLI, TUI, or library🧪 testingAutomated, simulated, UX, or hardware verification

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions