Community-registry audit ahead of listing.
Upstream 0.4.1 renames the model catalog (private/kimi-k2-6 →
private/kimi-k3, drops qwen3-vl-30b) and serves a status page at GET /,
so the package was documenting a stale model list and hiding a whole
surface. Export that page as a `ui` interface alongside the existing
`api` on one host, and unmask the API interface — its URL carries no
credentials, so masking hid the address for nothing.
PPQ_DATA_DIR stays unset deliberately. With it set, upstream persists a
browser-entered key to its own config.json while the StartOS-supplied
PPQ_API_KEY still wins at every restart, silently reverting the user.
StartOS owns the key via the action; the status page's form renders
disabled.
CI never ran: build.yml's PR target and tagAndRelease.yml's push
trigger both named `master` on a repo whose only branch is `main`.
Point them at `main` and reset all three workflows to the package
template, dropping the guard job retired in start-technologies@ed0dca2.
packageRepo now names the Start9-Community fork, which is where CI
runs, where the org's registry variables live, and where releases are
cut.
Also: drop three .catch handlers on file-model reads, which swallowed a
genuine read failure into "no key configured" — readOnce already
returns null for a missing file; pass null rather than an empty Mounts
for the unmounted subcontainer; inline two single-use interface consts;
and rewrite README/instructions against the writing guides, fixing a
YAML block that claimed a /data mount the package deliberately does not
make.
A PR build only compiles and packs, and build.yml falls back to
`start-cli init-key` when the secret is absent, so passing DEV_KEY only put the
real signing key on a runner that executes branch-authored code.
Replaces the placeholder brain-circuit icon with the PPQ flame
(flame2.png from the web app), resized to 256px / 34 KiB to fit the
40 KiB registry limit. Verified on the StartOS VM that the packed icon
renders and the service stays healthy.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- The proxy is stateless and env-configured; the 'main' volume is no
longer mounted into the container (config.json is read host-side)
- README/instructions note that backups contain the saved API key
- Upstream tagged v0.3.2 (matches package.json); submodule checked out
at the tag
Verified on the StartOS 0.4.0 VM: update installs over the previous
version, keeps the saved key, and reports attestation-verified health.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Verified on StartOS 0.4.0 (aarch64, QEMU/HVF VM): install/uninstall,
critical first-run task, config action, attestation health check, API
requests through the exported interface, logs, restart persistence,
and backup/restore.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Wraps the ppq-private-mode-proxy (git submodule, built from its own
Dockerfile) as a StartOS 0.4.0 service:
- Critical first-run task + masked action to set the PPQ.AI API key
- OpenAI-/Anthropic-compatible API interface on port 8787
- Health check reflects enclave attestation (proxy binds only after
attestation succeeds)
- x86_64 + aarch64, config backed up via the main volume
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>