Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,16 @@ Bosun turns the Logitech G13 into a cross-platform command console for AI coding

## Status

Phase 0 is complete on live Windows hardware. M1 software paths are mockable: a synchronous HID transport, a G13 TOML descriptor and codec, `MockTransport`, and `bosunctl device list|info|watch|record|rgb|leds|lcd test`. Live shared-input (AC-R1) is still pending a finger-on-key run.
Phase 0 is complete on live Windows hardware. M1 software paths are mockable: a synchronous HID transport, a G13 TOML descriptor and codec, `MockTransport`, and `bosunctl device list|info|watch|record|rgb|leds|lcd test`.

AC-R1 measured **fail both** (0 reports with LGS running and with LCore stopped) on 2026-09-20; details in `docs/hardware-notes.md`. Per `docs/PRD.md` AC-R1 / R1, **fail both stops M1** for Kyle's review — no HID redesign hop from this potato.

## Non-negotiable boundaries

- Stock OS HID stack only: no libusb, WinUSB/Zadig, kexts, or kernel modules.
- Dual-licensed under MIT OR Apache-2.0; GPL-derived source is not accepted.
- Do not consult or copy GPL G13 driver source. The measured protocol is documented in `docs/BOSUN-PLAN.md`.
- Logitech Gaming Software may overwrite LCD/RGB output. The first M1 hardware test must determine whether shared input reads work while LGS is running.
- Logitech Gaming Software may overwrite LCD/RGB output.

See `AGENTS.md`, `docs/PLAN-REVIEW.md`, and `docs/BOSUN-PLAN.md` before implementing. The product requirements, M1 acceptance criteria, and open owner decisions are in `docs/PRD.md`.

Expand Down
12 changes: 10 additions & 2 deletions docs/hardware-notes.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,15 @@
# Hardware Notes

## Pending M1 capture
## AC-R1 outcome (2026-09-20 WINDOWS-CU-20260920-01)

- **fail both**
- Path: `\\?\HID#VID_046D&PID_C21C#7&1562afa0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}` (usage_page=ff00)
- Run 1: LGS/LCore running (pid 8668) — 0 input reports in 15s (Kyle mash requested)
- Run 2: LCore stopped — 0 input reports in 15s (Kyle mash requested)
Comment on lines +7 to +8

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Verify keypresses before declaring fail both

If Kyle did not physically press keys during each exact 15-second window, zero reports is inconclusive—the earlier Phase 0 run already produced zero reports simply because nobody was at the keypad. These entries record only that a mash was “requested,” not that it occurred, yet the new README treats the result as authoritative and stops M1; record explicit operator confirmation for both runs or rerun them before classifying AC-R1 as fail both.

AGENTS.md reference: AGENTS.md:L26-L27

Useful? React with 👍 / 👎.

- bosun tip: `706ecd8` main
- Non-HW suite: 38+1 pass same session

## Still pending (not AC-R1)

- Shared input reports while LGS runs: not yet verified with physical keypresses.
- Physical mapping for bitmap names LEFT, DOWN, and TOP: not yet verified.
- Joystick center, cardinal extremes, corners, and diagonal envelope: not yet recorded.
Loading