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.