Repository navigation
v0.1.0
Shellboy Studio v0.1.0
Browser UI and thin local bridge, built from tag v0.1.0 at
1f26ec97c6e3cf3b8521422c4e430eddcb45ad32.
Exact Pair
Use Core v0.11.0, protocol 5, schema 39, official tag commit
4dc8f66a6c586db57a7a63a3a8be84e25999c95f. Older-owner compatibility and
protocol downgrade are not supported. Default features are next-shellboy,
next-connection-setup, next-tags and next-cwds; next-reply remains off.
Verified Evidence
- All three OS Checks and required Linux exact-pair job passed:
https://github.com/tya5/shellboy-studio/actions/runs/42545162766 - Release workflow, mandatory exact-owner acceptance (6 tests), all three native
builds, packaged version smoke and draft generation passed:
https://github.com/tya5/shellboy-studio/actions/runs/42545961767 - Hosted exact-owner checks build the verified public Core tag source. Separate
local acceptance uses the downloaded Core release binary and downloaded macOS
Studio archive with disposable data, a loopback mock provider and headless Chrome. - Downloaded archive checksums, safe extraction paths, bundled guide/doc links
(12 per archive), macOS CLI user/agent guides and embedded UI passed inspection.
Real-binary browser acceptance covers connection, synthetic send, saved answer
display, human ask/inbox/reply/removal, 16-duty cap with typed reply_limit and
retention of an unrelated Thread's pending question.
Downloads
Windows x86_64 ZIP, macOS arm64 tar.gz (deployment target macOS 14), Linux x86_64
tar.gz, plus SHA256SUMS. Verify checksums before running. No installer is included.
Limits And Scope
CI and headless browser evidence are not physical phone, accessibility technology,
Safari/Firefox or real-provider tests. Binaries are not signed/notarized. Legacy
17+ over-limit count/exactness/unknown-oldest rendering is synthetic-test evidence;
real legacy migration/17+ data was not tested or seeded. No paid API or user
conversation data was used. Attachments and additional platform targets are excluded.
Bundled README status statements describe the source candidate before publication;
preparation checklists and older validation notes are historical checkpoints, not
current pin/CI claims. This release page records the completed publication state
and exact evidence. Documentation status updates follow separately without changing
this audited tag. Earlier failed CI attempts remain visible and are superseded by
the successful exact-SHA run, not retroactively labeled successful.