Authoritative project documentation

ApiaryLens 0.1.0-rc.1

Release Status

This is a release candidate for MVP acceptance, not a stable release. It is intended for controlled UAT while deployment, recovery, accessibility, supply-chain, and diagram gates are completed.

Included

Installable offline-capable React PWA with local records, drafts, staged photos, synchronization, conflict foundations, and safe update behavior
Built-in owner, beekeeper, and viewer accounts with a durable authentication root, domain-separated password/session protection, opaque session rotation, throttling, and an atomic protected first-owner claim
Apiaries, hives, queens, equipment, inspections, photos, follow-ups, mite counts, feeding, treatments, harvests, timeline, and trend views
Hono API on Node 24/SQLite and Cloudflare Workers/D1/R2
Complete owner export, profile backup/restore foundations, and immutable migrations
Scout Bee Windows guided deployment executable for Cloudflare and Compose-over-SSH
.org, .app, .dev, .com, isolated synthetic demo, and synchronized docs

Known Release-Gate Limitations

Hyper-V Compose full UAT evidence is pending; the isolated Cloudflare data-path journey and the released Scout Bee guarded update pass at migration 0004.
Azure Compose automation is conditional and has not been proven.
The keyless repository signing workflow attests all six release subjects, including the in-toto statement, with the exact ApiaryLens workflow identity and a public transparency timestamp. The public CDN copies match those signed digests.
Final Lucidchart visual polish passes; manual accessibility/security review remains incomplete.
Native mobile applications, AI, sensors, video, passkeys, and OIDC are post-MVP.

Upgrade and Recovery

Do not update without a verified backup. Confirm pending PWA work is synchronized, verify the content-addressed artifact, apply ordered migrations, activate the new revision, and run health plus authenticated smoke tests. Use compatible application rollback only when migration boundaries permit; otherwise restore the complete pre-update backup.

Support Window

Release candidates receive best-effort support only until replaced by a newer candidate or the first stable release. Security defects and data-loss risks should be reported privately according to SECURITY.md.