[atomicdeploy]

Pakar maintained copies of its terminal editor, Telnet decoder and device TUI. Those implementations are now owned by atomicdeploy/portable-shell, merged upstream in PR #3. This consumes the exact four canonical headers at 52c5f7f94581806109e30f5c1ffd6c74ff5bff40 and replaces the local implementations with zero-state adapters.

This PR is stacked on #27 to keep the review focused. Authentication, property/command authorization, USB ownership, SSH/FTP/file transfer and hardware routing remain in Pakar. Hidden input/history scrubbing, completion/suggestions, secret/stale drafts and LED/pixel/game actions are retained. The shared view adds red rounded framing, magenta selection and Unicode direction hints. Optional diagnostics remain compile-selectable; no hardware API calls enter the shared library.

The same donor ledger now covers 21 files (17 historical entries plus four canonical components), with exact upstream hashes and drift assertions. Original source history remains intact. The latest parent branch is merged; generated comparison conflicts were resolved from the combined authoritative evidence rather than dropping either side.

Validation: tools/test-shell.ps1 passed production session/authentication/ownership fixtures, editor/TUI/completion, TCP/UDP loopbacks and command dispatch. Canonical upstream passed all 11 Windows/Linux/macOS/profile/ARM CI jobs; x86-64 and ARM component link audits have no external runtime dependencies after the project memory helpers. Actual emitted-byte Agave previews are upstream. Full Pakar firmware/CI and separately authorized physical device acceptance remain distinct; no production board was contacted or changed.

Tracks #29. Parent checkpoint 3ee583a is included, preserving its independent presentation storage and deterministic AVR receive fixture. Full board CI remains required.

[atomicdeploy]

Source-handoff coordination: I have read the four complete canonical component headers, the thin Pakar adapters, source manifest/drift assertions and ledger changes at 82c57af. Authentication, command authorization and hardware owners remain in Pakar; hidden input/history scrubbing, bounded parser/editor state and stale-field protections are retained. The freshly paginated conversation has no review findings. Parent #27 now passes repository health and CodeQL; SDK/Windows/Android jobs are running. I will merge the stack in dependency order only after final-head checks pass. The active integration worktree is preserved; no board or installed app was contacted.

[atomicdeploy]

Parent checkpoint now includes a separate host-presentation filename fix plus deterministic passive-RX failure fixtures (3ee583a). The former protects palette settings from persistent host-game saves; the latter fixes the Linux preflight race seen before SDK compilation. Parent CI is rerunning. Please preserve those changes when synchronizing the stack; the integration worktree remains untouched.