DiscussionBridge plugin v0.1.0-alpha.5 — REJECTED — DO NOT INSTALL
Pre-releaseREJECTED — DO NOT INSTALL
Phil's 2026-08-23 real-user Astro-hosted acceptance pass rejected this immutable prerelease.
- Qualified Discourse Core exposes no embedded avatar-menu Log Out control. Alpha.5's automated test synthesized that control, so its logout-return feature and required human step are unreachable in the production embed interface.
- The paired Astro adapter candidate also applied a competing
70vhCSS ceiling that clipped topic-progress/composer content at the host boundary. That independent adapter defect is being corrected separately.
The tag and release remain immutable dated evidence. Do not install, rewrite, retag, or silently replace v0.1.0-alpha.5. A corrected plugin must use a new prerelease tag, and the corrected adapter must pass the combined Astro-hosted human gate.
Preserved publication identity
- Tag:
v0.1.0-alpha.5 - Exact candidate/evidence head:
94f90811e5178752b1c54c16c15207dfe78e3bb6 - Functional production-code commit:
8e311968990a61f0fb3d07ae7757647d0783c71a - Qualified Discourse Core:
36698aae084678151dffa875d49c8d59216d2733 - Manifest: 71 files, 208,714 bytes, aggregate SHA-256
43bf58764f120f277d5f5f53ddb532e06605781f69409c8d3934596f2ed44b6d - Exact-head workflow: https://github.com/DiscussionBridge/discourse-discussion-bridge/actions/runs/32657120606
Superseded qualification claim
The automated suite passed at publication, but its synthetic logout-button proof did not establish that the real qualified Core embed renders an operator-accessible logout trigger. The human pass is controlling for that browser boundary and failed. Existing-user sign-in, new-user signup/activation, Reply, Like, Quote, edit, visible Post reply/Save edit, moderation, and mapped unlisted-topic behavior produced valuable positive evidence, but they do not override either blocker above.