The Bridge — DiscussionBridge for Discourse 0.2.0-alpha.19

DiscussionBridge family release candidate

DiscussionBridge for Discourse v0.1.0-alpha.6

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.

DiscussionBridge plugin v0.1.0-alpha.5 — REJECTED — DO NOT INSTALL

REJECTED — 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 70vh CSS 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.

DiscussionBridge plugin v0.1.0-alpha.4

REJECTED — DO NOT INSTALL

Human acceptance found two unresolved embedded UX defects and Phil added a required new-user sign-up/activation/return gate that this immutable candidate's public instructions do not contain. The tag remains immutable evidence and must not be rewritten. A corrected candidate requires a new tag.

DiscussionBridge plugin Alpha.4 prerelease candidate

This immutable prerelease corrects the human-install procedure exposed by the Alpha.3 preflight. It is not a production release and is not the final DiscussionBridge product Alpha.

Immutable identities

• Tag: v0.1.0-alpha.4
• Exact candidate: bc4b79199a252977dc7c50bfa191a0b79e423757
• Functional production-code commit: 1943923ec890d4686e088331ecfa62cd897add02
• Qualified Discourse Core: 36698aae084678151dffa875d49c8d59216d2733
• Manifest: 69 files, 181,852 bytes, aggregate SHA-256 59a3738805f7ba7ea963d46e002c730745919b06c17344dcf6c7c367ee73dd30

Qualification

• Official workflow: https://github.com/DiscussionBridge/discourse-discussion-bridge/actions/runs/32648686125
• 81 server/plugin examples passed.
• 7 browser/system examples passed.
• Lint, annotations, backend, and system jobs passed.
• Independent Code and Manual review passed this exact candidate and manifest.

Human-instruction correction

Alpha.3 human preflight stopped because the procedure required recording a protected rollback-configuration filename it never displayed. No configuration edit, rebuild, plugin installation, or forum mutation occurred. Alpha.3 remains immutable and rejected/do-not-install.

Alpha.4:

• separates the standard app and split web_only protected-copy commands into distinct copyable blocks;
• uses the accurate term container arrangement;
• verifies a readable regular source, refuses an existing destination, requires copy success, verifies a readable regular destination and byte identity, and prints ROLLBACK_CONFIG only after success;
• treats every error marker as a stop condition;
• continues to prohibit copying, editing, or rebuilding data for the split arrangement.

Required human gates

A human Discourse administrator must install this exact tag/SHA from the public instructions on:

1. sandbox-forum.discussionbridge.dev, standard single-container app;
2. dev-forum.discussionbridge.dev, split data + web_only, without touching data.

Each host requires its own real Astro-hosted signed-in interaction, reviewed signed-out sign-in, isolation, safe-at-rest, and rollback/reapplication evidence matched to its exact container arrangement. A failure creates another immutable candidate; this tag must not be rewritten.

DiscussionBridge plugin v0.1.0-alpha.3 — REJECTED — DO NOT INSTALL

REJECTED — 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:

1. A human Discourse administrator must install this exact tag/SHA from the public README on sandbox-forum.discussionbridge.dev using the standard single-container app procedure, verify the Astro-hosted authenticated iframe actions and reviewed signed-out sign-in behavior, then prove the documented rollback.
2. A human Discourse administrator must separately install the same exact tag/SHA on dev-forum.discussionbridge.dev using the split data + web_only procedure, without editing or rebuilding data, 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.

[REJECTED] DiscussionBridge for Discourse v0.1.0-alpha.2

Caution

REJECTED IN HUMAN ACCEPTANCE — DO NOT INSTALL. The public install and pinned rollback paths completed successfully, but Phil's real-user test proved that the behavior labeled fullInteractive rendered comments and handed interaction off to Discourse rather than completing native reply/actions inside the Astro-page iframe. Code review and Original Bridge Boss doctrine review independently confirm this is a product-contract blocker. The tag and commit remain immutable technical evidence. A corrected replacement prerelease candidate has not yet been published.

DiscussionBridge for Discourse v0.1.0-alpha.2

This immutable prerelease supersedes v0.1.0-alpha.0 and v0.1.0-alpha.1 for human installation. Both earlier tags remain unchanged as dated, zero-mutation preflight evidence.

Immutable identity

• Tag: v0.1.0-alpha.2
• Commit: 4e2d71edd0b97ddc61883f407a8d2872451b7285
• Internal plugin version: 0.1.0.alpha.2
• Qualified production-code ancestor: 50c4a92359f672a00b2242e99819a70813ebea19
• Qualified Discourse source: 36698aae084678151dffa875d49c8d59216d2733 (2026.8.0-latest.1)

Human-install corrections

• Uses read-only docker ps --format ... plus direct topology-file checks instead of unsupported launcher list.
• Honors each host's accepted recovery boundary; the disposable sandbox may use its separately accepted provider snapshot without an application backup.
• Adds a fail-closed pinned-upgrade path for an expected prior official installation: record the old SHA and configuration, replace only the immutable pin, never add a duplicate clone or run git pull, and rebuild only the matching application container.
• Separates rollback outcomes: fresh-install removal requires plugin absence; pinned-upgrade rollback requires the prior plugin present, clean, and exactly at the recorded prior SHA.

Install, upgrade, and rollback

Follow the public README and pin to the exact tag and commit above:

• standard single-container app: edit containers/app.yml, rebuild app;
• official split data + web_only: edit containers/web_only.yml, rebuild web_only only.

Never edit or rebuild data. Treat launcher output as protected because normal rebuild output can include environment values. After initial rebuild, all DiscussionBridge settings remain safe/default-off until the bounded enable/configure acceptance step.

Qualification

No functional plugin production behavior changed from the qualified candidate. The only executable-file change is the internal prerelease version header. Code review confirmed the prior exact-Discourse qualification remains applicable:

• 78/78 server/plugin examples;
• 4/4 browser/system examples;
• RuboCop across 47 Ruby files;
• i18n, ESLint, and Prettier checks.

The aggregate QUnit harness encountered upstream/resource-loading failures before product assertions; this is recorded qualification evidence and is not represented as a product-test PASS.

Required human acceptance before final Alpha

Install or upgrade this exact public identity separately on both supported topologies:

1. sandbox-forum.discussionbridge.dev — standard single-container app; its documented historical pin is upgraded to this candidate;
2. dev-forum.discussionbridge.dev — official split data + web_only.

Each host/topology requires its own accepted recovery identity, installed-SHA proof, migrations and safe-default checks, ordinary-forum health check, bounded enable/configure verification, and topology-matched rollback/removal evidence.

forum.repealobbba.org is not a substitute or third current release-gate install. Any later independent real-world proof there requires separate OBBBA authorization and recovery acceptance.

Do not rewrite or move this tag. Any further candidate correction receives a new immutable prerelease identity.

[SUPERSEDED] DiscussionBridge for Discourse v0.1.0-alpha.1

Warning

SUPERSEDED — DO NOT INSTALL. Human preflight identified an expected historical pinned plugin hook, but this release did not provide the required public pinned-upgrade procedure. The pass stopped before any configuration edit, rebuild, or forum mutation. This tag remains immutable dated evidence. Use v0.1.0-alpha.2, pinned to 4e2d71edd0b97ddc61883f407a8d2872451b7285.

DiscussionBridge for Discourse v0.1.0-alpha.1

This immutable prerelease supersedes v0.1.0-alpha.0 for human installation. Alpha.0 remains unchanged as dated failed-preflight evidence; its human pass stopped before any configuration edit, rebuild, or forum mutation.

Immutable identity

• Tag: v0.1.0-alpha.1
• Commit: ddffa4c9b92ac8a6293a2600102125272200a870
• Internal plugin version: 0.1.0.alpha.1
• Qualified production-code ancestor: 50c4a92359f672a00b2242e99819a70813ebea19
• Qualified Discourse source: 36698aae084678151dffa875d49c8d59216d2733 (2026.8.0-latest.1)

Corrected human preflight

• Replaces the unsupported ./launcher list command with read-only docker ps --format ... output.
• Retains direct containers/app.yml and containers/web_only.yml topology checks and the ambiguous-topology stop.
• Uses the accepted host-specific recovery boundary: application backup, provider snapshot, or both according to forum role.
• Allows the separately accepted DiscussionBridge disposable sandbox snapshot as its recovery point without requiring an unnecessary application backup.
• Keeps stricter recorded recovery policy for durable preproduction and production forums.

Install and rollback

Follow the public README procedure and pin the clone to the exact tag and commit above:

• standard single-container app: edit containers/app.yml, rebuild app;
• official split data + web_only: edit containers/web_only.yml, rebuild web_only only.

Never edit or rebuild data for this plugin. Preserve the topology configuration and accepted recovery identity. Treat launcher output as protected because normal rebuild output can include environment values.

All DiscussionBridge settings remain safe/default-off after initial rebuild and health verification. Enable/configure only during the bounded acceptance step.

Qualification

No functional plugin production behavior changed from the qualified candidate. The only executable-file change is the internal prerelease version header. Code review confirmed the prior exact-Discourse qualification remains applicable:

• 78/78 server/plugin examples;
• 4/4 browser/system examples;
• RuboCop across 47 Ruby files;
• i18n, ESLint, and Prettier checks.

The aggregate QUnit harness encountered upstream/resource-loading failures before product assertions; this is recorded qualification evidence and is not represented as a product-test PASS.

Required human acceptance before final Alpha

Install this exact public identity separately on both supported topologies:

1. sandbox-forum.discussionbridge.dev — standard single-container app;
2. dev-forum.discussionbridge.dev — official split data + web_only.

Each host/topology requires its own accepted recovery identity, installed-SHA proof, migrations and safe-default checks, ordinary-forum health check, bounded enable/configure verification, and topology-matched disable/rollback/removal evidence.

forum.repealobbba.org is not a substitute or third current release-gate install. Any later independent real-world proof there requires separate OBBBA authorization and recovery acceptance.

Do not rewrite or move this tag. Any further candidate correction receives a new immutable prerelease identity.

[SUPERSEDED] DiscussionBridge for Discourse v0.1.0-alpha.0

Warning

SUPERSEDED — DO NOT INSTALL. The first human preflight exposed an unsupported launcher inspection command before any configuration edit, rebuild, or forum mutation. This tag remains immutable dated evidence. Use v0.1.0-alpha.1, pinned to ddffa4c9b92ac8a6293a2600102125272200a870.

DiscussionBridge for Discourse v0.1.0-alpha.0

This is the immutable public plugin prerelease candidate for DiscussionBridge Alpha human-install acceptance. It is a prerelease, not the final DiscussionBridge Alpha product release.

Immutable identity

• Tag: v0.1.0-alpha.0
• Commit: 590a2256d286cbe918801317ec0626ad4de0ea17
• Qualified production-code ancestor: 50c4a92359f672a00b2242e99819a70813ebea19
• Qualified Discourse source: 36698aae084678151dffa875d49c8d59216d2733 (2026.8.0-latest.1)

Install and rollback

Follow the public README procedure and pin the clone to the exact tag and commit above. The README supplies separate procedures for:

• standard single-container app (containers/app.yml, rebuild app);
• official split data + web_only (containers/web_only.yml, rebuild web_only only).

Never edit or rebuild data for this plugin. Preserve the pre-install configuration and rollback identity. Treat launcher output as protected because normal rebuild output can include environment values.

All DiscussionBridge settings must remain at their safe/default-off state after the initial rebuild and health check. Enable and configure only during the bounded acceptance step described by the README.

Qualification

The candidate production code passed:

• 78/78 server/plugin examples;
• 4/4 browser/system examples;
• RuboCop across 47 Ruby files;
• i18n, ESLint, and Prettier checks.

The aggregate QUnit harness encountered upstream/resource-loading failures before product assertions; this is recorded qualification evidence and is not represented as a product-test PASS.

Required human acceptance before final Alpha

The same exact published identity must be installed from the public instructions and separately accepted on both supported topologies:

1. sandbox-forum.discussionbridge.dev — standard single-container app;
2. dev-forum.discussionbridge.dev — official split data + web_only.

Each host/topology requires its own rollback identity, installed-SHA proof, migration and safe-default checks, ordinary-forum health check, bounded enable/configure verification, and topology-matched disable/rollback/removal evidence.

forum.repealobbba.org is not a substitute or third current release-gate install. Any later independent real-world proof there requires separate OBBBA authorization and recovery acceptance.

If either human installation exposes a candidate defect, do not move or rewrite this tag. Correct the defect under a new immutable prerelease identity.