You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 94a7b2d
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/specifications/App/TDD.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -506,6 +506,38 @@ UI reads down (watch providers) and writes up (call `Connection` methods / DAO m
506
506
-**Test compatibility:** a test overriding `connectionProvider` directly with a `FakeConnection` still **wins** (the override replaces the derived body), so the existing widget/golden suite (`shell_harness.pumpShell`) is untouched. New connect-flow tests inject `FakeScanner` + a `ConnectionFactory` returning `FakeConnection` + a fake `BleReadinessSource` through a `PbleConnectionManager`, or override `connectionManagerProvider` with a fake manager — no fake radio / fake `BleLink` needed (FR-CONN-7, D5).
507
507
- The `ConnectController` (`Notifier`) projecting the manager into `ConnectState` for the connect surface lives in `lib/connect` ([§4.8](#48-libconnect--scanconnect-flow-ui)); it is the one place with the connect-flow intents.
If an uncancellable factory returns a board after supersession, close that
527
+
exact stale board once without attaching it or changing the current selected
528
+
board, phase, or error. Failures from stale work remain with that operation;
529
+
they must not overwrite a newer session. Manager disposal prevents new work,
530
+
releases its streams/notifiers even on board-close failure, and is idempotent.
531
+
No new wire command, permission flow, board identity gate, reset, version bump,
532
+
or automatic connection retry is introduced by this clarification.
533
+
534
+
Host regressions must exercise the real HELLO-ready `PbleConnection` over a
535
+
recording fake `BleLink`, including physical-disconnect call/state, shared
536
+
dispose completion, late HELLO, cleanup failure, external transport ownership,
537
+
replacement and late factory results after disconnect/disposal. Existing
538
+
connection/facade and wire-conformance tests remain required. Host tests alone
539
+
do not fill the physical ordinary-disconnect/reconnect rows on either tablet.
540
+
509
541
### 6.3 Single active writer / serialization
510
542
511
543
The app is one client to one board (SEC-2). `PbleConnection` serializes mutating operations (`runFile`/`runSource`/`putFile`/`delete`/`mkdir`/`rename`/`softReboot`) through an internal queue so commands cannot interleave; a `RUN` while running surfaces `EBUSY` as `EBusy` ([§14](#14-error-handling--mapping)) rather than corrupting state (FR-RUN-3). Read-only ops (`listDir`, `deviceInfo`) and `stop` are not blocked behind a long transfer beyond correctness.
Copy file name to clipboardExpand all lines: docs/specifications/App/specs.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1002,6 +1002,7 @@ implementation:
1002
1002
-**FR-CONNECT-4** — The screen MUST list **saved boards** and reconnect them by remembered identifier; on link loss the app MUST auto-reattempt and in-flight transfers MUST resume per [protocol.md §5](../protocol.md#5-file-transfer-the-reliability-core). MUST (*source: PRD §8.1, §19.3, §13.1; verify: integration; story: A-03/A-22*)
1003
1003
-**FR-CONNECT-5** — The flow MUST be scan → connect → use only: no pairing-code step, no account, no session-lock/heartbeat, and no board-identity gating (the non-goals of [PRD §4.3](../prd.md)). MUST (*source: PRD §8.1, §9.6, §19.3, §4.3; verify: widget; story: A-22*)
1004
1004
-**FR-CONNECT-6** — The connect flow MUST refuse a board with an unsupported `proto_version` and prompt to update the firmware/app rather than failing silently. MUST (*source: PRD §18.3; verify: widget/integration; story: A-10/A-22*)
1005
+
-**FR-CONNECT-7** — Ordinary Disconnect, replacement of the selected board, and disposal of an owned connection MUST close that connection's actual BLE link, not merely detach the UI. Teardown MUST be idempotent, abort pending protocol/transfer work and release owned subscriptions; a close failure MUST remain an error, not a successful physical-disconnect claim. A superseded or cancelled connection attempt MUST NOT publish its late result or disturb a newer session, and MUST close any link it eventually acquires. Direct engine-backed connections MUST NOT acquire ownership of externally supplied transports. MUST (*source: FR-BLE-4/5, FR-CONN-5/7, SEC-2; verify: actual protocol engine with recording fake links, manager races, real iPadOS/Android disconnect/reconnect HIL*)
1005
1006
1006
1007
**Connected Board-info identity slice — FROZEN (`[docs]` 2026-08-22, additive to FR-CONNECT-2).** The testable acceptance criteria are:
0 commit comments