Verified on 16 September 2026#
The backend, library, and console are hosted over HTTPS. CLI 0.1.0 and the core/client/CLI crates are published. Six native release jobs, public native installation, Cargo installation, automated backend/CLI/browser suites, and a real production CLI sign-in have passed. Current membership disclosure enables authorized console administration. Signed IAM management notifications have been received by Honeycomb.
These checks do not mean every application has a published package or that every cross-service workflow has passed production acceptance.
Integration work still required#
| Area | Current boundary |
|---|---|
| Briefcase storage | Honeycomb needs all four delegated upload/commit/read/link-access grants and fresh user consent. Live end-to-end package storage acceptance remains pending. |
| Public activation | Complete immutable review/activation mapping and downstream archive-access reconciliation before claiming public distribution acceptance. |
| Existing IAM applications | Supported adoption must preserve identity and secrets. The accepted IAM snapshot lacks the authoritative active webhook URL needed by the current configuration workflow. |
| Shared testing | App-owned authority, credential/key versions, additive imports, lifecycle/retention receipts, and test-only management need remaining service contracts. |
| Bundles | Honeycomb owns the design, but this release has no complete bundle UI/API/CLI workflow. |
| Notifications | Management notification receipt is verified; recipient-scoped workflow delivery has additional integration work. |
No interface should label remote work completed until the responsible service confirms it. Keep legacy-writer and scheduled-testing cutovers disabled until replacement workflows are accepted.
Briefcase as a Honeycomb application#
The current Briefcase storage API is compatible with Honeycomb's reserve/transfer/commit/read/link-access transport. Briefcase still needs a six-target Honeycomb package/release workflow, an updater that respects Honeycomb-owned installations, adoption of its existing tos>briefcase identity, and the shared-testing participant contract. Do not create a duplicate Briefcase IAM identity or rotate its production secret merely to list it.
The repository keeps detailed integration engineering notes in IAM contract review and Briefcase compatibility. Those notes supplement these user guides and can change as services ship.