Skip to content

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

Pre-release
Pre-release

Choose a tag to compare

View all tags
@phillipnhenry phillipnhenry released this 23 Aug 06:05
v0.1.0-alpha.2
4e2d71e

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.

Assets 2
Loading