2.6 KiB
Alpha readiness pass — 2026-10-20
Source changes
- Native macOS/Linux remains the default installer; Docker remains opt-in.
- Native installation now includes the authenticated, dependency-free web client, Go server and ntfy under one per-user supervisor. Raw API defaults to loopback.
- Native service enable/status/disable select the existing owned installation, not a separate developer server/database. Existing credentials and valid host harness defaults are retained; no harness is installed or upgraded.
- Fresh native installs explicitly enable pipeline authoring. Existing missing or
false roles remain execution-only unless the operator chooses
./install --allow-authoring. No live role or definition was changed. - Five primary generic starters: small code change/review, research/fact-check, summarize documents, compare options, plan/checklist. All five earlier keys remain available (eight entries total). Models bind from configured defaults.
- README and tester walkthrough now prioritize native browser setup and explain separate browser/ntfy channels. Closed-app browser push remains unsupported.
Evidence
The scratch lifecycle smoke validates all primary drafts, creates a definition explicitly, checks definition transfer and verifies restart persistence. It does not call providers or mutate the operator's database.
web/test/ui-smoke.mjs --scratch exercised actual catalogue reads and template
validation/publication against a current-source loopback server and scratch
database with explicit authoring enabled. All eight entries were present.
Desktop and 390px captures include create dialog, success and resulting list;
card geometry checks catch clipped stage counts and document overflow.
Captures are in the approved OpenCode temporary
alpha-template-browser-captures/ directory, not committed private evidence.
Native installer and service tests use isolated prefixes, fake dependencies and mock launchd/systemd. Docker setup regressions remain separate and opt-in. Go build/vet, source tests, Python installer tests and browser tests are verification of source behavior, not proof of a successful operating-system installation.
Release boundaries
No production deployment, service restart, provider login, phone/device test, or live definition publication was performed. Original histories and branches were preserved. Native Linux installation, real login autostart, fresh-provider OAuth and real starter inference still need an operator/tester trial. A Linux cross-build or systemd mock must not be reported as those checks passing.
Deployment remains the operator's step under internal/server/AGENTS.md.