DiscussionBridge plugin v0.1.0-alpha.3 — REJECTED — DO NOT INSTALL
Pre-releaseREJECTED — DO NOT INSTALL
Human preflight on 2026-08-23 exposed that the public procedure required the administrator to record the protected rollback-configuration filename but never displayed that expanded filename. The test stopped before any configuration edit, rebuild, plugin installation, or forum mutation. This tag remains immutable evidence and must not be rewritten. Use the next corrected immutable prerelease candidate when published.
DiscussionBridge plugin Alpha.3 prerelease candidate
This is an immutable prerelease candidate for human installation acceptance. It is not a production release and is not the final DiscussionBridge product Alpha.
Immutable identities
- Tag:
v0.1.0-alpha.3 - Exact candidate commit:
075388cdc6dbfe1112ee0a82dc0cec497e2c913b - Production-code commit:
1943923ec890d4686e088331ecfa62cd897add02 - Qualified Discourse Core:
36698aae084678151dffa875d49c8d59216d2733 - Acceptance manifest: 69 files, 179,466 bytes, aggregate SHA-256
bee6355abed2c48c8a8bfde87af78f2dd27cdd390d88d60a65ac9200fbeda085
Qualification
- Official Discourse plugin workflow: https://github.com/DiscussionBridge/discourse-discussion-bridge/actions/runs/32632385381
- 81 server/plugin examples passed.
- 7 browser/system examples passed, including native empty-state Reply, existing-post Reply, persisted Like, Quote submission, fail-closed readiness, and isolation.
- Lint, structure, annotations, backend, and system jobs passed.
- Independent Code and Manual review passed the exact candidate and manifest.
Alpha.3 correction
For completed mapped comments-only full_app=true requests, DiscussionBridge now fails closed when Discourse Core full-app embedding is unavailable. Health reports in-page interaction readiness and exact blockers. Qualified Discourse Core continues to own the native composer, Reply, Quote, Like, edit, authentication, authorization, CSRF, and moderation behavior.
Required human release gates
Before this candidate can be accepted:
- A human Discourse administrator must install this exact tag/SHA from the public README on
sandbox-forum.discussionbridge.devusing the standard single-containerappprocedure, verify the Astro-hosted authenticated iframe actions and reviewed signed-out sign-in behavior, then prove the documented rollback. - A human Discourse administrator must separately install the same exact tag/SHA on
dev-forum.discussionbridge.devusing the splitdata+web_onlyprocedure, without editing or rebuildingdata, and produce its own acceptance and rollback record.
A failure does not rewrite this tag. It creates a new immutable prerelease candidate.
Supersession history
v0.1.0-alpha.2 remains immutable and visibly rejected/do-not-install because real-user testing proved that its claimed fullInteractive behavior handed interaction off to Discourse instead of completing it inside the Astro-page iframe. Alpha.3 supersedes Alpha.2 for installation testing; it does not rewrite it.
Immutable README timing note
The README inside this immutable tag records the prepublication candidate state that existed immediately before the tag and release were created. Its sentence saying Alpha.3 was not yet published is dated prepublication evidence and is superseded by this release record. The current main-branch README records the completed publication without moving or rewriting this tag. The executable install-and-acceptance procedure in the tag is unchanged.