[Frontier] [LIVE16-01] Collect exact-build Linux, account and native-device evidence #431

Parent

#392 — #392; complete S16 target #392.

Model tier

Frontier: this slice requires judgment about protected authority, lifecycle/recovery or a new cross-client/service contract; exact new APIs and migrations are not yet settled.

Context to read

AGENTS.md; CONTEXT.md; docs/agents/workflow.md; docs/specs/S16-rakazo-experience.md; docs/specs/S15-conversational-autonomy.md; ADR 0064 and ADRs 0074–0077; docs/design/S16-rakazo-experience.md; docs/design/S16-mobbin-research.md. Reuse the completed design research; do not repeat broad Mobbin discovery.

Starting implementation/contract surfaces: tests/s16-binary.live.test.ts; docs/contracts/s16-binary-files-v1.md; docs/evidence/. Read their current definitions and relevant tests before selecting changes. Paths with braces denote existing module families, not settled new signatures.

Deliverable

Run the remaining real Linux parser/VM/browser, selected model vision, app/OAuth, microphone and native-device task matrix with owner-provided inputs at a concrete tested build. Existing #340/#341 S15 evidence remains separately owned.

Baseline and readiness

Audited stack head 17b814220371cd1e2126be2ec9bd9753537f69e6; main remains the pre-S16 baseline. #398/#399/#403/#404 are open drafts, not merged/live acceptance. Existing S15 services are reusable baseline, and #400/#401 supply draft text/binary custody. No new behavior is claimed here. Branches/PRs and issue ownership were inspected on 2026-11-05; this new ticket has no implementation claim. Recheck at dispatch. Preserve the primary-owned jit/402-s16-file-memory branch.

Human/device/account evidence only, blocked until the exact concrete artifacts and deterministic evidence are available.

Implementation steps

1. Recheck ownership, branches/PRs, prerequisites and exact source baseline. Compare existing implementation, pinned Rakazo reuse and a simpler alternative; record the chosen tradeoff and versioned contract before coding.
2. Prepare exact opt-in commands/artifact hashes and redactable evidence checklist before asking for owner input.
3. Run generation-3 rootless Linux parser isolation and separately actual image challenge against selected supported route.
4. Run real modern website login/2FA, protected takeover, app action, desktop/mobile notification and continuous voice scenarios.
5. Store installation-specific addresses/private evidence only in ignored .local; publish safe outcome/digest/gap summary.
6. Integrate the authored experience using real service facts, English/Thai dictionary keys in their designated files, accessible loading/error/empty/reconnect states and current capabilities. For non-UI evidence work, verify those states instead of inventing new UI. Record migrations, compatibility and exact build evidence.

Acceptance criteria

• No fixture or simulator substitutes for real host/device/account outcome.
• Failure leaves honest pending/failed row and does not enable unsupported capability.
• No credentials/private screenshots enter GitHub or ordinary exports.
• Existing [Frontier] [EVID15-01] Prove the protected boundaries and the GitHub scenario on the tested build #340/[Frontier] [CUT15-01] Install S15 fresh on jit-vm with owner acceptance and a recoverable install #341 are neither closed nor duplicated by S16 evidence.
• Deliverable works end to end through its actual owning service/client; source presence, transport success and model prose alone are insufficient.
• No S14 default, S15 opt-in, installed policy, historical private scope or owner-host configuration changes without its separate explicit transition.
• New contracts, unresolved limits and exact revision/evidence are recorded; applicable upstream licenses, immutable provenance and modified-file notices ship.

Tests and evidence

1. No fixture or simulator substitutes for real host/device/account outcome. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
2. Failure leaves honest pending/failed row and does not enable unsupported capability. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
3. No credentials/private screenshots enter GitHub or ordinary exports. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
4. Existing [Frontier] [EVID15-01] Prove the protected boundaries and the GitHub scenario on the tested build #340/[Frontier] [CUT15-01] Install S15 fresh on jit-vm with owner acceptance and a recoverable install #341 are neither closed nor duplicated by S16 evidence. Use scripted models, protocol fixtures, fake clocks and barriers for deterministic cases; assert actual resulting state/bytes/effects.
5. Run relevant existing module/composed regressions plus the new scenario suite; for rendered behavior, exercise the real bundle in English/Thai, keyboard and mobile widths. Record exact test paths/commands in the PR after implementation selects them.
6. Keep real host/account/device checks opt-in and evidence-labelled; no absent credential blocks independent deterministic work. Public evidence contains hashes/outcomes only; installation-specific details belong in ignored .local records.

Requirements

S16-AC01, S16-AC02, S16-AC03, S16-AC04, S16-AC05, S16-AC06, S16-AC07, S16-AC08, S16-AC09, S16-AC10, S16-AC11, S16-AC12, S16-AC13, S16-AC14, S16-AC15, S16-AC16, S16-AC17, S16-AC18, S16-AC19, S16-AC20, S16-AC21, S16-AC22; FR-01, FR-02, FR-03, FR-04, FR-05, FR-06, FR-07, FR-08, FR-09, FR-10, FR-11, FR-12, FR-13, FR-14, FR-15, FR-16, FR-17, FR-18, FR-19, FR-20, FR-21, FR-22, FR-23, FR-24, FR-25, FR-26, FR-27, FR-28, FR-29, FR-30, FR-31, FR-32, FR-33, FR-34, FR-35, FR-36, FR-37, FR-38, FR-39, FR-40, FR-41, FR-42, NFR-01, NFR-02, NFR-03, NFR-04, NFR-05, NFR-06, NFR-07, NFR-08, NFR-09, NFR-10, NFR-11, NFR-12, NFR-13, NFR-14. Retain S15 authority decisions and FR/NFR identifiers.

Blocked by

• [Frontier] [EVID16-01] Run the complete deterministic cross-client acceptance matrix #430: prerequisite owning contract/delivery; currently open, not merged acceptance.

Contracts used/delivered

Use current owning POLICY, DATA15, TEAM, MEM, WORK, CHAT and S16 client/file contracts where relevant, plus Schway's supported public host surface. Specific inputs and proposed delivery: tests/s16-binary.live.test.ts; docs/contracts/s16-binary-files-v1.md; docs/evidence/. The Deliverable and ordered steps define the missing contract outcome; freeze version, schemas, migration/recovery and conformance fixtures in the implementation ADR/PR. Proposed operations are not already supported APIs. A demonstrated missing engine seam requires a bounded public-only reproduction and a linked Schway contract ticket, never an internal import or duplicate runtime.

Out of scope

Other tickets' outcomes, hosted multi-user SaaS, marketplace operation, upstream branding, silent billing, replacing Schway, general historical data conversion, and unapproved live deployment. This ticket is evidence/adoption work, not permission to skip owner input or alter unrelated hosts.

Do not

Do not use source/model/tool output as authority; expose credentials, sensitive-site sessions or protected state to working execution (trusted-site sessions are the S16-D09 exception); remove guards before proof; auto-retry unknown effects; weaken or bypass the S16-D07 human-required list or let anything but the in-chat owner decision approve it; treat current stack limitations as scope cuts; add model attribution; use implement-parallel; alter #402 ownership; self-merge or deploy. No placeholder controls or fabricated success.

Definition of done

Run the exact opt-in commands selected in the concrete evidence checklist, record tested release/device/engine hashes, safe outcomes and remaining gaps. git diff --check must pass for evidence edits. No live action precedes required owner input. PR body includes Closes #431 and Refs #392, contract versions, tested head and honest pending evidence. No self-merge; parent #392 remains open until full accepted outcomes.

Requirement-specific acceptance and evidence

The dependencies below gate final matrix completion, not every individual live scenario. A concrete, authorized parser/image or device subcase may be collected as soon as its own exact artifact is ready; unrelated voice/client work must not hold that evidence hostage. Record per-row prerequisite digests and pending inputs.

Owner revision 2026-11-06

Grok-style autonomy (S16-D06–D11, ADR 0084) and Telegram removal (ADR 0085) apply. Only the S16-D07 human-required list waits for the owner, approved by a one-press in-chat card; GitHub push/PR/review replies/merge after required checks are the product default; trusted sites may keep sessions in the working VM browser while sensitive sites stay in the protected browser. Jit has no messaging channel; notifications use Web Push (#441). Policy/approval changes belong to #442.

S16-AC18 now means Web Push notifications; there is no messaging channel to evidence.