# Coherent-shell closeout by operator acceptance — 2026-10-10

The project operator accepted the installed coherent shell and explicitly
waived additional proof gathering:

> continue but you dont have to gather that proof ive already confirmed its fine carry on it's all good

[operator-report.json](operator-report.json) records the exact conversation
instruction, installed artifact and evidence identity, and limits. The earlier
“it all worked land it” accepted the requested Home/All Apps/Terminal/Overview/
Help navigation checks on the exact temporary candidate. The guarded installer
then selected that bundle persistently and observed untouched ordinary boot.
[Combined installation evidence](../combined-board-candidate-2026-10-10/README.md)
contains the actual source/bundle/kernel/runtime identities, all installed hashes,
fresh boot ID, four active services, protected rollback and reviewed native Help.
The current instruction follows the coordinator’s explanation that the broader
proposal remained open for named camera, gesture and theme proof. It replaces
those extra proof-collection gates with operator acceptance; no further board
interaction, build, recording or measurement was performed for this closeout.

Worktree `$HOME/tmp/k230-coherent-closeout-2026-10-10`, branch
`closeout/coherent-integration-2026-10-10`, base `972e013a1749d9bbf765ea012df5898697cdeffb`.
Owned scope: this change and its archive, four affected capability files,
this evidence directory and the change’s work-board status entry.
No board, serial or build reservation.

## Disposition of the remaining tasks

| Task | Closeout basis | What was not performed |
| --- | --- | --- |
| 0.3 | Record acceptance of the actual production Rust shell running on the board; historical probe comparison is waived | A new Rust/C/Qt comparative probe trial or resource/cadence benchmark |
| 5.1 | Record accepted shell routing/recovery and explicit capture waiver | New 60-second route video or per-case physical matrix |
| 5.2 | Record accepted live-card interaction; preserve existing card source/QEMU and operator evidence | New reverse/throw/refusal camera trial |
| 5.3 | Record accepted drawer/Settings/Help behavior and waive further discovery/conflict captures | New scroll/long-press/keyboard-conflict outcome table |
| 5.4 | Accept implemented notification/Settings behavior using the operator’s broad closeout instruction and existing host/QEMU proof | Individual notification typing/critical/failed-action physical trials |
| 5.5 | Record the user’s existing measurement deferral; implementation and board measurement are already owned by the side-edge/motion successor | A trace tool run, timing/frame/CPU/RSS numbers or a budget pass |
| 5.7 | Record accepted app switching with prior implementation/QEMU proof and the capture waiver | New per-direction/hold/end/exit/conflict camera matrix |
| 5.8 | Actual installed selection, hashes, ordinary boot and native UI checks already passed; additional physical/theme matrix waived | A selected-generation restoration trial: no active generation/report existed before or after installation |
| 6.4 | Accept installed visual/navigation behavior and waive a further six-surface dark/light recording | New six-surface camera/contrast/theme-apply trial |

The current tasks were revised to require this documented disposition rather
than checking the old unperformed test instructions. The
[superseded requests](superseded-verification.md) preserve every original open
task and command. Source, host, QEMU, injected-board, native-board and operator
evidence retain their distinct provenance. Quantitative and individual-case
UNVERIFIED markers remain where no matching observation exists.

## Accepted scope and outstanding implementation

The accepted navigation topology comes from the already-landed Home spec:
app → Overview → pinned Home → All apps. The old proposal’s “Home is the
live deck” text is reconciled before sync; it does not replace the accepted
pinned Home with an old deck-only design. Help opens a deliberately selected
navigation aid, without permanent navigation chrome.

The earlier authorized split remains intact. Qualified side-edge Back,
general compositor at-down touch ownership, and motion trace implementation/
board measurements remain unimplemented/open under
`the-shell-gets-side-edge-back-and-motion-trace`. The waived comparative probe
experiment is not a claim that Rust was benchmarked against C or Qt. The
separate Qt evaluation proposal also remains open. No new successor or hidden
implementation requirement was invented for this acceptance closeout.

The theme parent still has actual applicable consumer coverage and a
removed-source recovery policy conflict. The theme-performance proposal still
has profiler/momentum source work. This instruction removes extra proof
collection as a gate for accepted behavior; it does not finish those source
changes or silently pick the unresolved policy.

## Validation and publication

Narrow closeout commands:

```sh
openspec validate the-handheld-presents-a-coherent-shell --strict
openspec archive the-handheld-presents-a-coherent-shell --yes --json
openspec validate --all --strict
python3 scripts/build_site.py
python3 tools/work-status.py
```

The archive CLI applies the reviewed deltas to `runtime/handheld-shell-design`,
`runtime/device-settings`, `runtime/notification-center` and `runtime/shell`.
Main specs are not hand-edited. Existing requirements and scenarios outside
this delta are retained. CI and the actual published work/evidence pages are
checked for the landed revision after push; publication results are reported
in the final handoff rather than claimed in advance here.

The first committed-tree site check at source `7ce6e866` exited 2 during the
work-board data pass: the already-archived Wi-Fi Settings entry still named
the coherent shell’s old active dependency key. Coordinator `/root` owns that
failure and corrected only this directly affected dependency reference to the
new archive key. The private host log is `$HOME/tmp/k230-acceptance-coherent-site.log`.
No Astro build or hardware action was attempted in that failed check; the full
site command is rerun against the corrected committed tree before publication.