DiscussionBridge for Discourse v0.1.0-alpha.6
Pre-release
Pre-release
·
55 commits
to main
since this release
DiscussionBridge for Discourse v0.1.0-alpha.6 is an immutable prerelease candidate for the two-host human acceptance gate.
Exact identities
- Tag/evidence commit: 787e3c0
- Production correction commit: edbf55b
- Qualified Discourse Core: 36698aae084678151dffa875d49c8d59216d2733
- Final workflow: https://github.com/DiscussionBridge/discourse-discussion-bridge/actions/runs/32673128928
- Manifest: 70 members; 204,604 bytes; aggregate SHA-256 237d5fb3e58706ff035295d0e7d38c24d3744b7aedf5a9de2c6c0877123bbff4
Correction
- Retains Core ownership of authentication, logout cleanup, and sessions.
- Invents no embedded logout control.
- In an actual child iframe on its unchanged, server-attested completed-mapping route, intercepts only Core's exact You were logged out / Refresh action and asks Core's logout helper to reload the mapped route instead of rendering / inside Astro comments.
- Signed route qualification is bound to mapping ID, topic ID, database-precision mapping version, and exact class. Forged direct, incomplete, ordinary, top-level, post-navigation, and generic Refresh boundaries fail closed.
Required human gates
- Install separately on sandbox-forum.discussionbridge.dev standard app and dev-forum.discussionbridge.dev split web_only. Retain one acceptance record per host.
- Use the public pinned-upgrade/rollback instructions and exact SHA above.
- Repeat the corrected adapter sizing/credit checks plus Reply, Like, Quote, edit, signed-out Refresh, sign-in, signup, moderation, and rollback checks.
v0.1.0-alpha.5 remains immutable rejected evidence and must not be installed. Do not rewrite or retag any prerelease.