Linux qualification and release limits

Canonical source is fwdslsh/fhold on GitHub. Linux CLI/Admin downloads and signed multi-architecture container images are published through GitHub releases. Alpha and beta releases are not stable releases. fhold owns the generic images, CLI/Admin, runtime contracts and reusable tests; host deployment and third-party installers are outside the product boundary.

Release-specific gates run through the GitHub release workflow. The workflow builds Linux x64/ARM64 CLI and AppImages, tests images on native x64 and ARM64 runners, signs published images and checks uploaded asset bytes before publishing. ARM64 Admin is cross-built and is not native-startup-qualified. The scoped reviewed advisories remain disclosed exceptions, not clean-scan claims.

Beta.1 source qualification

The corrected 0.1.2610061043-beta.1 fixes installation-failure recovery's busy state without changing the image runtime or provider API. It supersedes the earlier beta candidate without replacing its published bytes.

On October 6, all 657 enabled source tests passed; optional architecture/image tests remain separately gated. Type checks, lint, CLI compilation and Admin bundling passed. Admin's 121 tests include 842 assertions; actual Chromium renderer checks passed 107 assertions, including delayed recovery and retry. The complete native Electron/Docker management walkthrough passed fresh install, two named instances, Apps and deferred restarts, portable content, cold directory recovery, full stopped export/import with keys/history preserved, and read-only reopening in a second process. Its main report contains 49 screenshots and 53 audit records, with no serious/critical accessibility findings or horizontal overflow. Native confirmation responses were simulated; no vendor requests were made and provider readiness was explicitly unattempted.

Separate live Go checks against the published earlier beta completed explicit Test/Use/Continue, post-restart readiness and a guarded MCP response. The native provider-settings regression also passed all seven stages with that actual Assistant and controlled compatible endpoints, without vendor requests or container/OpenCode-process replacement during settings changes. These do not qualify every vendor, actual local model engine, remote pairing or ARM64 Admin. See Admin qualification and provider verification for scope and repetition. Every corrected public artifact still requires its own release workflow, checksum/signature verification and packaged Linux x64 startup check.

October 5 source qualification

The source adds an explicit stopped, same-instance scope alongside portable content. It does not change the published alpha.6 artifacts or automatic Assistant checkpoint format. See the user guide for coverage, confirmation, empty-target and external-storage requirements. The candidate also refreshes AKM to CLI 0.9.26 and plugin 0.9.26202610051302 in all three Assistant harnesses; see the harness guide for the pin and installation contract.

Linux x64 verification on October 5, 2026:

• All 611 source tests passed with loopback socket and native-history checks enabled, with no failures or skips. Type checks, lint, CLI compilation and Admin bundling passed. All Compose profiles validated, including the restored home's secret and mount boundaries.
• Full-scope fixtures preserved all instance trees, extra root files, native SQLite/WAL conversations, private keys, image pins, dependency links and ordinary permission metadata. Changed/incomplete inventories, unsafe paths, occupied destinations and running/paused/restarting writers were refused. Interrupted imports remained blocked from startup; portable defaults were unchanged.
• The actual Electron/Docker walkthrough refused a live export, preserved cancellation and a read-only preview, exported after a normal confirmed stop, and imported into an empty folder without installing first. Native confirmation responses were simulated; renderer, IPC, shared library, Docker and the native database were real. Identity and keys remained unchanged, no containers started during import, and the original OpenCode session was retrieved through the authenticated API after an explicit start. Window dimensions stayed unchanged.
• The sidebar now has only the wordmark, a named recent-instance picker and navigation, without a subtitle, status footer, visible path or Refresh button. Overview owns the path and container status. Real rendered checks covered direct switching, cancellation, the Welcome route, keyboard navigation, long names, automatic status recovery, narrow layout, 200% zoom and 44px actions. The complete Electron/Docker journey passed with 51 accessibility/layout audits and no violations or horizontal overflow. Background reads preserved drafts, keys and configuration baselines; switching waited for in-flight reads. No dependencies or production window resizing were added.
• An AKM-guided design specialist reviewed actual native startup captures and approved the compact two-choice Welcome, progressive naming/optional folder step and named recent list. Read-only compatibility/name metadata uses the existing recent list, without another settings store. Existing-folder opening refuses empty/unavailable homes; only explicit new setup accepts them. Native tests covered cancellation, Back/focus, preserved drafts, no home seeding, duplicate-free recents and 200% keyboard scrolling to Choose folder/Continue.
• A second native Electron process reused only the disposable test profile and automatically opened the last-used installed instance. Preferences and stack intent stayed unchanged, and no containers started. Manual switching returned to Welcome and stayed there across another renderer reload, with unchanged window dimensions. Unit tests covered safe fallback for missing, empty, foreign and broken previous homes without choosing an older instance automatically.
• A fresh Linux x64 Admin AppImage from this source revision passed actual packaged startup with normal host Chromium sandboxing and an isolated profile. The native release smoke exercised Welcome, the renderer/bridge and named instance preparation. The preview retained the alpha.6 version label; it did not replace the installed Admin or change an existing instance.
• During development, one native-window narrow/zoom traversal failed the existing recovery timing-field assertion once. The repeated complete journey passed the unchanged assertion; its failure diagnostics now include non-secret field, saved-value and focus details. The cause was not established, so this is not evidence that a timing-field defect was fixed. Only the test harness resizes windows. The UI tests do not reset timing fields to make an assertion pass.
• One later repeat stalled while capturing the unchanged Agent settings page. Only its owned Electron test process was stopped, and the launcher cleaned up its disposable stack. The cause was not established. Screenshot tests now bring their own window forward and bound the entire render/audit wait, not only the final capture call. The subsequent complete native walkthrough and second-process reopening gate passed; no production focus, sizing or runtime behavior was changed to compensate.
• All three Linux x64 images rebuilt and passed standard startup smokes. The new AKM pins passed actual OpenCode, Claude and Codex session/prompt recall, both default-on and explicitly disabled native workers, preserved customized settings, native managed policy, real conditional keep-alive ticks and cold directory recovery. Recall passed again after recovery. The duplicate older OpenCode-plugin CLI dependency is gone; no runtime updater or vendor patch was added. The existing dependency audit policy passed with its unchanged reviewed build-only exception. These are isolated, account-free runtime checks, not vendor sign-in or remote-client reconnection evidence.
• Isolated homes/projects were used; existing user instances were not stopped or changed. A management fixture bypassed provider readiness for this UI journey: the free provider rejected the setup probe. These checks do not qualify a fresh provider sign-in, vendor remote reconnect, external storage or ARM64 execution.

This is historical source/build evidence, not certification of later artifacts.

Alpha.6 changes and local evidence

0.1.2610050714-alpha.6 adds managed recovery configuration and stopped-writer operations to CLI/Admin, plus a simpler System view with Installation details, Recent logs, Import / export and Ephemeral container support in that order. The two data-transfer features retain separate contracts; recovery is opt-in.

Local Linux x64 verification of the implementation before release:

• All 576 source tests passed with loopback socket and native-history checks enabled, with no failures or skips. Type checks, lint, shell syntax, all-profile Compose and secret/mount audits passed.
• The actual Electron/Docker flow covered directory initialization, live status, a fresh accepted checkpoint, deferred changes and persistent pending activation, confirmed restore and true loss of custom files and SQLite outside persistent mounts. Restoring missing members preserved surviving native state.
• Setup, export/import omission acknowledgments, independent instances, compact System layout and stable window sizing were exercised. Automated accessibility checks covered normal and narrow layouts and 200% zoom. Native confirmation responses were simulated; the UI, IPC, Compose and recovery engine were real.
• Concurrent recovery status publication covered 1,200 reads during 300 atomic replacements. Malformed, oversized, symlink and non-regular status files remained rejected; capture-time file mutation checks were not relaxed.
• All three standard local images built. Native directory and Blob-emulator recovery passed, including repeated cold restore, as did packaged x64 Admin startup. These are synthetic recovery/account fixtures, not live hosted account renewal or provider readiness claims.

Each published artifact still requires its own GitHub workflow gates and post-publication checks. Live Blob storage, network-mount behavior, remote client reconnection and measured RPO/RTO remain deployment-specific qualification. ARM64 Admin startup is not qualified by the local x64 tests.

The published alpha.6 passed GitHub release run 37276782651 from f20630e0019e5261a74671fbebfc543f721ebe06. Source quality, all six native x64/ARM64 image gates, native history and real directory recovery passed, as did CLI, MCPB and packaged x64 Admin gates. The corresponding main CI run also passed.

Independent post-publication checks validated the complete downloaded checksum and asset-manifest set, an anonymous x64 CLI download, all three anonymous image pulls and amd64/arm64 manifests, and image signatures bound to the exact GitHub workflow, issuer and release commit. The downloaded x64 Admin passed its actual AppImage startup on Linux with normal host sandboxing and an isolated profile. ARM64 Admin remains build-only.

An existing live instance was upgraded through the released CLI after a private full stopped-state backup. Before application writers restarted, exact hashes confirmed preservation of 10,252 existing operator/native account files and all 208 sessions, 6,630 messages and 30,251 message parts. Effective intent was unchanged apart from managed image pins; recovery remained disabled. All three services became healthy with zero restarts and no pending activation. Native API authentication, a real no-tool provider response, authenticated MCP tool listing and a read-only session call passed. Discord reconnected without a test message; Claude remained signed in and both native workers restarted. This does not qualify a fresh remote-client pairing or vendor reconnect, and both integrations remain experimental.

Alpha.5 changes and local evidence

0.1.2610050129-alpha.5 includes Admin's confirmed/deferred container activation and persistent pending-restart banner, plus mount-aware runtime recovery. Portable backup remains the reviewed-content/fresh-install path; its archive does not gain runtime authority or automatic container-path exclusions.

Linux x64 local verification of this candidate:

• Full source suite with socket tests enabled, type checks and lint passed.
• Seventeen focused mount-policy tests covered namespace visibility/overmounts, explicit and discovered boundaries, missing mounts, absent SQLite/WAL guards, ownership changes, immutable-publication fencing, partial-restore journals and reviewed fresh-namespace transitions. These fixtures do not qualify SMB/NFS.
• The actual candidate image passed cold replacement and offline restore with real nested read-only/read-write binds and an external root outside its catalog. External SQLite-named content was never traversed or restored; newer independent contents survived. Native sessions, registered databases and custom files restored, periodic/final checkpoints published, and ownership released.
• Blob-emulator transport conformance and the same native-image mount/replacement checks passed, including stale publisher rejection and failed upload handling.
• Real AKM recalls passed through OpenCode, Claude and Codex's native plugins. These are synthetic account/trust fixtures, not real vendor account readiness.
• Recovery smokes configure the calling non-root UID/GID for private bind mounts, matching the managed-install contract instead of assuming UID 1000. All three native AKM recalls also passed under UID 1001 without modifying the image.
• CLI compilation, Admin bundling and unsigned MCPB packing passed. Admin's retained real Electron/Docker E2E covered deferred save without a restart, pending-state preservation after closing/reopening, confirmed activation and unchanged window sizing; no provider account was needed for that management path.

The published alpha.5 passed GitHub release run 37251908317 from 9fdedf7603ebcf2d7081eaa11ba99a795ba5ecbe: source quality, all three native x64/ARM64 image gates, real directory recovery on both architectures, native CLI artifacts and packaged x64 Admin startup. ARM64 Admin remains cross-built only.

Independent post-publication checks verified every downloaded checksum/manifest, x64 CLI and AppImage startup, anonymous Assistant pull, and all three image signatures against the exact GitHub workflow, issuer and source commit. A fresh CLI-created instance used the public image by default, served authenticated native shell/file requests, retained its container during deferred settings changes and cleared pending state after healthy activation. Portable backup restored its workspace marker into another fresh installation without copying native databases. Only disposable fixtures were used; existing instances were not updated.

Actual SMB/NFS/FUSE behavior, live hosted account reconnect and measured RPO/RTO remain external qualification. Discovery is opt-in and known required mounts should be explicitly declared. Native dependency compatibility rules are unchanged.

Alpha.4 scope

0.1.2610041911-alpha.4 adds native managed harness policies, the global --name/-n instance selector and a public Claude Desktop extension download link. See upgrade notes for retained homes, compatible image pins and custom-hook behavior. The managed-policy review records source and real-image checks; each alpha.4 artifact still requires its own release gate. Do not treat historical alpha.2/alpha.3 counts below as alpha.4 results.

Published alpha.3 evidence

Alpha.3 was published by successful GitHub release run 37189889821. Its standalone Linux CLI/Admin, MCPB, checksums and manifest are public. All three Docker Hub images are signed and support amd64/arm64. Native x64/ARM64 runtime gates, downloaded x64 CLI/AppImage startup, fresh CLI installation, authenticated OpenCode access and conditional keep-alive passed. These immutable artifacts predate managed policies and must not receive alpha.4's managed-only mounts.

Dependency-refresh verification

On October 4, 2026, the refreshed candidate passed these Linux x64 checks:

• Frozen workspace install, type checks, lint and all 477 product tests, with no failures or skips. Native-history tests used the newly built Assistant image; loopback socket tests were enabled. No workspace dependency was reported outdated by bun outdated --recursive.
• CLI compilation and actual-binary configuration-boundary tests, Admin bundle and x64 AppImage startup, standard unsigned MCPB packing, all-profile Compose validation on a CLI-created empty home, shell syntax and workflow linting.
• All three image builds and normal startup smokes. Assistant verified npm/npx 12.2.0 as non-root stdio launchers, all three native AKM recalls, preserved Codex decisions, changed-hook re-review and remote-worker failure isolation.
• Cold-container directory and Blob-emulator recovery, including native SQLite, custom paths, account/trust fixtures, final checkpoint and ownership release. These use synthetic data, not real vendor accounts. Azurite's API-version check is disabled because it does not yet implement the shipped SDK's service version; this proves emulator transport/recovery behavior, not live service compatibility.
• Trivy 0.75.0 found no critical advisories in any image and no fixable high advisories in Guardian or Portal. Assistant still has the three documented npm bundle findings. The reviewed unsigned-MCPB build-tool exception also remains.

The workspace uses the latest stable published direct dependencies checked that day. Upstream packages retain their own nested pins: for example, akm-opencode still depends on akm-cli 0.9.21 internally while the installed command is 0.9.24. No override was added to force a different upstream SDK implementation. No live deployment, provider request, remote-client pairing or native ARM64 run is qualified by these local checks. Cross-version checkpoint restore remains unsupported; refreshed native dependency versions require their own checkpoints.

Qualified alpha.2 evidence

The previously locally qualified Linux artifacts and all three images are 0.1.2610040221-alpha.2. Qualification on October 4, 2026 covered the exact built artifacts, not subsequent source changes. Original versions, bytes and verification receipts remain immutable.

• Frozen offline dependency installation, package type checks and lint passed.
• All 473 product tests passed without failures or skips, including real loopback sockets, image-backed security and native-history preservation.
• Assistant, Guardian and Portal passed their standard startup image smokes, including non-root execution, workspace Bun configuration isolation, baked helpers/skills and restart checks. Assistant received no Docker socket or Guardian/Portal credentials; services were non-privileged and dropped all Linux capabilities.
• Native Linux x64 compiled CLI build/startup and compiled configuration-boundary regressions passed. The x64 AppImage passed extraction/startup, renderer and bridge checks. The standard unsigned MCPB pack and manifest validation passed.
• Linux ARM64 CLI and AppImage cross-builds passed, with the extracted Admin ELF verified as aarch64. This is build-only evidence, not native ARM64 execution.
• Compose validated all three profiles on a CLI-created home. Real native API, authenticated Guardian MCP, provider readiness, restricted scheduler work and restart checks passed through ordinary product interfaces. Unauthenticated native API and MCP access were rejected; credential-scoped catalogs and a real guarded request were checked before and after restart.
• Native-history recovery preserved complete original conversations and later appended work across restart. Reviewed unfinished calls became terminal interrupted errors without replay; imported task definitions stayed inactive.
• Actual AKM recall passed in OpenCode, Claude Code and Codex. Native Codex hook decisions were preserved, and changed definitions required review. A real Claude native-client tool request and allowed Discord interaction were confirmed; these do not qualify every account, client or portal configuration.

The setup path used the packaged CLI and native provider flow. A real no-tool readiness request succeeded, and only the untouched Guardian moderator placeholder was replaced with the exact verified provider/model. Tests did not repair image PATH, permissions or settings to conceal product defects.

Use the testing workflow, Admin verification and release operations to repeat the relevant gates. Changed source or artifact bytes require a new release identity and their own verification; source cleanup does not re-certify existing images or deployments.

Remaining gates

Native Claude/Codex workers remain experimental. Supervisors default on and preserve explicit off decisions; native sign-in, consent and workspace trust remain user choices. Alpha.4's built-in hooks use managed registration, not personal approval. Process status is not client/tool readiness. Codex defaults to workspace-write; outer container isolation must be explicit. Account renewal and reconnect after recovery require separate live confirmation.

Windows/macOS packaging and native ARM64 Admin startup remain unqualified. Public OAuth, a live Slack account, target-host network mounts and measured recovery capacity/RPO/RTO remain separate gates. The unsigned MCPB build-tool advisory exception is scoped to packing, not a clean-audit claim; see release operations.

Recovery requires exact recorded native dependency versions. It is not a schema upgrade engine or zero-loss replication. SQLite remains local; directory backup destinations need coherent atomic filesystem semantics. See Assistant recovery for scope and failure behavior. No foreign-home adoption, compatibility layer, SSH management or cross-host publishing bridge is implemented.

View this page on GitHub