OBBBA Human Runbook: onebigbeautifulbill.us and forum.repealobbba.org

Status: existing proof-page package migration and live fullInteractive interaction verified; fresh-import Alpha gate open Environment: current live proof lane plus local canonical source
Last verified from workspace facts: 2026-07-21
Companion: OBBBA Machine Runbook

Alpha feature lock: This runbook remains part of the cumulative locked Alpha proof set. New OBBBA work must close an existing gate, fix exercised behavior, or be approved explicitly as a scope change. The separate DiscussionBridge.dev dogfood gate does not replace an OBBBA gate.

The separate DiscussionBridge.dev two-direction dogfood gate is now complete at apex commit d68ffc4: Astro-managed blog topic 37 and Discourse-managed wiki topic 36 were independently verified live. This evidence does not change or close any remaining OBBBA-specific gate. Sanitized dogfood verification record.

For release reuse, distinguish the full automated attribution gate inside package 73/73 from the bounded docs-scope gate inside the 20-source/21-page docs build. Neither records Manual Boss semantic approval. The exact release still needs its own Attribution and Licensing: PASS / FAIL / N/A, reviewed paths, and sanitized review record. Candidate b09dbce has that separate PASS; see its sanitized record.

This runbook covers the first real OBBBA Discussion Bridge lane:

Current package import behavior also supports explicit --source-mode discourse-imported|discourse-managed and per-manifest sourceMode (1731547, Code Boss PASS, 72/72). Existing OBBBA entries remain discourse-imported; this capability does not change their ownership or authorize writeback.

public site: https://onebigbeautifulbill.us
community/source forum: https://forum.repealobbba.org
proof page: https://onebigbeautifulbill.us/title-i/10101-impact/
source topic: https://forum.repealobbba.org/t/sec-10101-re-evaluation-of-thrifty-food-plan-impact/434

Spelling matters: the canonical forum hostname is forum.repealobbba.org.

Never place passwords, API keys, tokens, private account values, or production secrets in this runbook, screenshots, tickets, or chat.

1. What This Lane Does

The forum holds the source discussion and community history. The Astro/Starlight site presents a polished public impact-analysis page. The current Section 10101 page was manually imported, pruned, and polished from Discourse topic 434.

The current relationship is intentionally one-way:

forum.repealobbba.org topic 434
              |
              | manual import and prune
              v
onebigbeautifulbill.us/title-i/10101-impact/
              |
              | display the original discussion
              v
forum.repealobbba.org topic 434

Astro must not write the polished page back to the Discourse first post unless a human explicitly promotes the page to astro-managed.

Visual placeholder: approved source-topic-to-public-page diagram.

2. Current Ownership And Review Lanes

Responsibility	Lane
OBBBA/Discussion Bridge implementation	Bridge Boss
Discussion Bridge code review	Code Boss
OBBBA product manuals and runbooks	Product Boss
Manual quality and public/private review	Manual Boss
Cloudflare, DNS, forum, and account operations	Phil/Ops

3. Current Site State

The canonical active repository is:

https://github.com/OneBigBeautifulBill/onebigbeautifulbill.us.git

The canonical local source lane is:

C:\CodeProjects\Projects\OBBBA\sites\onebigbeautifulbill.us\astro

The current site uses Astro 7, Starlight, Mermaid, the Cloudflare adapter, OG image generation, and astro-discussion-bridge. The Alpha integration uses the unique packed artifact vendor/astro-discussion-bridge-0.1.0-alpha-69846cf-64a151bd.tgz; it is not the final public Alpha distribution. The intended public path is the exact reviewed registry astro-discussion-bridge@alpha package after release gates pass.

Stop if: work is pointed at the legacy-source directory, a copied deploy tree, a different forum spelling, or a different repository without an explicit source-ownership decision.

4. Source-Mode Safety

The proof page currently contains:

discussionSourceMode: discourse-imported
discussionSync: false
discourseTopicId: 434
discourseTopicUrl: https://forum.repealobbba.org/t/sec-10101-re-evaluation-of-thrifty-food-plan-impact/434
discussionImportedFrom: https://forum.repealobbba.org/t/sec-10101-re-evaluation-of-thrifty-food-plan-impact/434
discussionImportPolicy: manually-pruned
discussionCommentsDisplay: fullInteractive

Before editing or building, confirm discussionSync: false is still present. Editing the Astro page does not promote it. Promotion requires a recorded human decision, an ownership review, and an explicit change to the source mode.

This MDX file uses Windows CRLF line endings. The package recognizes both LF and CRLF frontmatter boundaries and preserves the existing line-ending style when it updates frontmatter.

Stop if: the guard is absent, the topic ID is not 434, the source URL changes unexpectedly, or anyone proposes writeback without explicit promotion.

5. Read And Edit The Proof Page

Open:

src/content/docs/title i/10101-impact.mdx

The page should contain:

the Section 10101 impact analysis;
the image src/assets/obbbanotso.png with alt text One Big (not so) Beautiful Bill;
links back to the source topic/footnotes;
the Discourse topic ID and URL;
fullInteractive comments configuration;
discussionSync: false.
an import of astro-discussion-bridge/Discussion.astro.

Preserve the imported source relationship even when polishing prose in Astro or GitCMS. Forum-only boilerplate may be pruned, but source attribution and the discussion link remain.

6. Build And Preview

From the canonical Astro project root:

npm run build

You should see the Section 10101 route generated along with site assets and search output. The known Starlight warning may appear:

Entry docs -> 404 was not found

The verified build also reported the existing large-chunk warning and punycode deprecation. The deployment-shaped build passed after installing the packed Alpha artifact. An npm clean-install wrapper timed out after 184 seconds, but the package resolved afterward and the complete build passed; a timeout alone is not proof of either success or failure.

Sandboxed builds may also fail when OG image font fetching needs external network access or Wrangler tries to write profile logs. A deployment-shaped build previously passed with normal network/profile access.

Stop if: the Section 10101 route is missing, the source-mode guard changes, a real credential appears in output, or a new build failure is dismissed as a known warning without verification.

7. Verify The Discussion

The selected proof mode is fullInteractive because the page is long enough to show the Discourse interaction after the article and because the OBBBA lane is intended to encourage forum participation.

Verify:

Open https://onebigbeautifulbill.us/title-i/10101-impact/.
Confirm the public analysis renders completely.
Confirm the discussion area points to topic 434 on forum.repealobbba.org.
Test logged-out behavior.
Test logged-in reply, like, quote, and sign-in behavior when the full app embed is enabled.
Test desktop and mobile layout.
Confirm the public page remains readable when the forum is unavailable.

This page explicitly links topic 434. In that case, the full-app embed must use the topic ID; it does not require Discourse to reconcile the public page URL to an owning topic. A page-URL embed-info 404 or an exact search with no owner is a separate diagnostic result, not evidence that topic 434 is broken.

If the embed does not open topic 434, inspect the generated topicId, forum host, full-app setting, CSP/embed configuration, and fallback link. Use the native full display as a deliberate fallback only after recording the decision.

Screenshot placeholders: desktop and mobile Section 10101 page with the discussion beginning below the article body.

Video placeholder: signed-out page load followed by Discourse sign-in and a test reply on the approved test topic/account.

The existing proof-page signed-in reply item is complete. The approved browser session created post 12, containing Test post after Discussion Bridge update, at https://forum.repealobbba.org/t/434/12. Topic 434 now has 12 posts. The test account identifier is intentionally omitted from this runbook.

8. Current Key Model

The Discourse bot user is obbba-bot. The settled key model is:

granular publishing/runtime key for future routine bridge operations;
separate global/admin-capable diagnostics key for setup checks;
diagnostics key kept out of runtime and deployment paths.

The key values belong in the approved credential vault. This runbook records only names, purposes, and scopes.

The publishing scopes are:

categories:list
categories:show
posts:edit
posts:list
search:show
tags:list
topics:write
topics:update
topics:read
topics:status

The current proof page is import/display-only. Do not run publish or sync against it merely because publishing credentials exist.

9. Verified Alpha Integration And Next Pass

Bridge Boss completed the local package migration without a Discourse write:

The site consumes the unique packed Alpha artifact.
Astro is configured for Starlight, the canonical site/forum URLs, fullInteractive, and publishOnBuild: false.
The proof page imports the package Discussion.astro component.
All source-mode, topic, manually-pruned content, image, alt text, and comments settings were preserved.
The installed OBBBA artifact’s integration suite passed 50/50. Package main later passed 51/51 with Code Boss final PASS for full rendering parity; that later package change was not deployed to OBBBA in this pass.
The deployment-shaped OBBBA build passed.
Generated HTML contains topic ID 434, fullApp=true, the correct forum URL, and the correct fallback topic URL.
No publish, sync, import, overwrite, or other Discourse write occurred.

Code Boss’s P2 review correction is included: the shipped embed declaration now distinguishes an explicit topicId from a discourseEmbedUrl, while allowing the optional fullApp and embedHeight settings.

The corrected safe preview recognized linked topic 434 and skipped the page with reason discussionSync is false: 0 created, 0 updated, 1 skipped, 0 unchanged, and 0 dry-run. The earlier not linked result was caused by CRLF frontmatter parsing and did not write to Discourse.

The release pass replaces packed integration artifacts with the exact reviewed registry astro-discussion-bridge@alpha artifact corresponding to the GitHub prerelease commit after all npm/GitHub release gates pass.

The imported-page integration now uses a Starlight MarkdownContent page-boundary override plus an extended docsSchema, so custom bridge frontmatter survives and every imported Markdown page receives its discussion. Do not add a second per-page <Discussion> component; the old explicit 10101 instance was removed to prevent duplication.

The final tag-routed policy applies the hero with required exact alt text and the opt-in community-call-to-action prune profile to all five topics. Each body matches the independently verified Discourse raw prefix. The verified CTA suffix removals are 456 characters for topic 434, 511 for 747, 549 for 751, 453 for 752, and 441 for 753; no CTA footer remains.

The four-route matrix now passes locally, in a clean production-shaped build, and live. Topics 747, 751, 752, and 753 each return HTTP 200 with exactly one correctly bound discussion and the intended hero/prune policy. Together with the existing topic 434 proof, this closes the broader live matrix gate.

The reviewed refresh mechanism is the ordered discussionbridge-imports.json manifest. It records topics 434, 747, 751, 752, and 753 in deliberate order. Every entry requires the live TITLE-I tag, uses fullInteractive, a hero with required alt text, the community CTA prune profile, and a safe explicit output. Topic 434 keeps its curated 10101-impact.mdx destination.

Every route has two contracts. WHEREFROM identifies the Discourse source, topic/order, category when applicable, and required source tags. WHERETO fixes the Astro content root, output file, public route, and Astro navigation lane. In this Starlight implementation, that lane is the mapped Title sidebar group. Validate both before writing; never infer either side from latest activity.

The live outer Astro page renders the Mermaid SVG and five HTML tables. The ordinary Discourse view of topic 434 also renders Mermaid and its tables, but the fullInteractive embed still shows raw Mermaid code and weak table styling. That cross-origin iframe is Discourse-owned, so Astro transforms and CSS cannot alter it. Embedded Discourse CSS, targeted through the new class hook, is the supported immediate table path; Mermaid remains an open Discourse embed issue.

Package commit d7800d7 completed the separate Astro-rendered full parity work: lazy Mermaid 11 rendering, readable tables, public opt-out, and resilient failure behavior. Code Boss passed it with 51/51 tests and both demo builds. No OBBBA content write or deployment occurred during that package-only pass.

The package validates the whole batch before writing, stages every result, and uses atomic creation or rollback so one bad entry does not leave a partial refresh. Keep using import-existing --manifest ... --overwrite; do not replace it with a blanket update-all command that loses per-page policy.

The Discourse category ID and required topic tags for this proof lane are not yet recorded in the durable source reviewed for this runbook. They must be confirmed before any command that could create or update topic metadata.

Stop if: the explicit topic changes unexpectedly, a write is proposed for this imported lane, or category/tag values are guessed.

10. Deployment And Domain Checks

The Astro configuration uses:

site: https://onebigbeautifulbill.us
Cloudflare worker name: onebigbeautifulbill
production branch: main

Live deployment evidence:

Package implementation/manual commit 7aadcf63c76b8ebd9e0c9383b5c7386ad704396e is on main.
OBBBA integration commit f277171 and deterministic deployment fix e9c279dbe1b0bec512ff7fcf0c9ec6f17f0dd6b8 were pushed.
The reviewed manifest site slice was committed and pushed as 64a4f94.
A clean detached build found a tracked stale starter page that a dirty local deletion had hidden. Removing that page was isolated and pushed as a225f00; the clean build at that exact commit passed.
Tag-safe curated outputs were reviewed in package commit 69846cf; the OBBBA Title-lane site slice received Code Boss PASS and was pushed as bd591c9.
Worker onebigbeautifulbill deployed successfully as version cde279d5-1c27-452c-964f-59d8dfd7c320 at https://onebigbeautifulbill.systems-b95.workers.dev.
The canonical proof page returns HTTP 200 and contains the package signature: topic 434, fullApp=true, the correct forum and fallback URLs, and the hero image. The legacy data-topic-id renderer is absent.
Topic 434 remains visible, open, unarchived, and has 12 posts. A signed-in reply was created and verified after deployment.
publishOnBuild remains false; deployment performed no publish, sync, or import write.
Canonical smoke checks returned HTTP 200 for topics 434, 747, 751, 752, and 753; each route has one correct discussion boundary and the expected hero/prune state, exact alt text, canonical topic URL, and no CTA footer. The sidebar exposes Title I through Title X and five unique Title I destinations.

Unrelated unstaged OBBBA changes and superseded untracked package artifacts were left untouched.

wrangler.jsonc now pins the operational Cloudflare account ID so deployment is deterministic. The private account label is intentionally omitted from this public-facing runbook. The broader OBBBA-versus-Citizen-Activist ownership decision remains open.

Verify the deployed commit, HTTPS, the Section 10101 route, the source topic, the embed host setting, and comments behavior. Cloudflare account ownership and the OBBBA-versus-Citizen-Activist ownership boundary remain an Ops decision; do not invent or relocate that boundary in this runbook.

11. Recovery

Cloudflare-backed forum evidence

The source forum, forum.repealobbba.org, is served through Cloudflare CDN. The completed OBBBA evidence is therefore also a production CDN compatibility proof for the workflows exercised here: diagnostics/API reads, imports, reconciliation and source-topic links, fullInteractive comments, signed-in replies, five live source disclosures, and no writeback.

Do not generalize this into support for every CDN/WAF/cache configuration. Keep Discourse API and JSON paths, embed/full-app routes, authentication/cookies, and websockets intact. If an API, embed, or session result differs from direct origin behavior, inspect Cloudflare cache/WAF handling before retrying writes or changing the bridge.

If topic 434 is missing or deleted, do not recreate it automatically.
If the Astro page is missing, recover it from the canonical repository and verify its source metadata before deploying.
If comments fail, keep the public analysis readable and retain a direct link to the forum topic.
If the deployment appears stale, verify the commit and forum state, then test cache bypass or a narrowly scoped purge.
If a credential leaks, revoke it, replace it through the private vault path, and rerun diagnostics. Never record the replacement value here.

12. Release Sign-Off

Deferred Demo And Credit Work

Add clearly labeled proof pages on onebigbeautifulbill.us for two bounded alternate targets: forum.citizenactivist.network (“A community of activists”) and forum.discussionbridge.dev demo/credit topics. Each page must select exactly one target explicitly. Production OBBBA pages and source content remain on forum.repealobbba.org.

The live proof record must also retain selected onebigbeautifulbill.us pages bound to forum.repealobbba.org, and record the separate edge from multiple Astro/public sites into that same forum. Those four edges distinguish page/lane-level target selection from the many-to-one convergence proof.

The Alpha proof must use the same selected OBBBA page for both forum.repealobbba.org and forum.citizenactivist.network through an explicit ordered target list. The package design and implementation are reviewed and complete at 60e41e1; bounded OBBBA live adoption completed at 36df91c. It claims real one-page multi-forum operation, but not the future general administration plane. The planned comments-boundary credit must remain configurable, secondary, accessible, and outside site content. Its final wording and default remain undecided.

Live verification on the canonical 10101 page passed: protected source and primary discussion remain Repeal OBBBA topic 434; exactly one accessible Additional discussions navigation links Citizen Activist topic 9. Topic 9 is visible in public category 5 with the Bridge-created tags. Exact retry returned unchanged, so no duplicate was created. Source topic 434 retained 12 posts and its first-post update time, proving no source writeback.

Interaction addendum: Citizen Activist topic 9 accepted a live reply as post 2. The OBBBA page continued to embed primary Repeal OBBBA topic 434 and exposed the independent Citizen Activist conversation through the accessible Additional discussions link. This is interaction/presentation proof for the already- closed bounded gate; its scope is unchanged.

Content correction evidence: OBBBA commit 4fffe5e removed only the stray flowchart editing instruction; the requested Mermaid block remained. A target-specific dry-run and live sync updated only Citizen Activist topic 9 and its binding state. Repeal OBBBA source topic 434 stayed protected and unchanged. Topic 9 retained two posts and Mermaid source, with the instruction absent. The clean build and deployment passed (Worker 344dfe40-8b71-4ff4-aea2-bc831af9c51d); the canonical Astro Mermaid rendered, primary topic 434 and additional topic 9 remained correctly presented.

For future additional links, follow Every connection has a job: explain who the discussion is for and what readers can do there, not only the forum name. Keep independent reply streams separate. CAN may support the opposite direction on separate page/topic pairs, but never make this same item writable in both directions.

The correct publishing lane is src/content/docs/title i, route base title-i, active target citizen-activist. A broad dry-run first exposed the wrong root/ index and malformed route before any write. Always correct route drift before publication.

For the proof page, use discussionTargets as the ordered target list, discussionPublishTargets as the writable subset, and discussionSourceTarget to protect the imported OBBBA source. Confirm each result appears under its own discussionTargetBindings entry. Set discussionPrimaryTarget before linking the second discussion; the primary must render and the additional target must appear as an accessible named link.

Run one explicit --target at a time. If the Citizen Activist publication fails after the Repeal OBBBA binding succeeds, preserve the successful binding, inspect the target-specific sanitized failure, and retry only the failed target.

Source disclosure gate

The package source-disclosure feature is implemented and reviewed at a9d2097 (68/68). OBBBA adoption commit aa7846d installed the reviewed artifact and wired DiscussionSource near the article start through the canonical Starlight MarkdownContent boundary. Code Boss adoption review, clean detached install, and production build passed; publishOnBuild remained false.

Live verification passed on all five canonical Title I routes. Each contains exactly one Content source aside, one View the source discussion link to the correct forum.repealobbba.org topic, exact imported wording with the Repeal OBBBA Forum label, and the existing discussion boundary. No Discourse write occurred. Source-disclosure adoption and the bounded Citizen Activist multi-target proof are complete; wider topology and administration remain separate scope.

The exact detached install reported 10 dependency audit findings: 1 low, 1 moderate, and 8 high. Route dependency review separately; do not run an automatic audit fix. Credential record cleanup remains inside protected storage and must not expose paths or values here.

For the exact OBBBA release candidate:

Code Boss pass/fail recorded.
Blocking code-review edits completed and re-reviewed where required.
Bridge Boss technical verification completed.
Manual Boss quality review completed.
OBBBA Human and Machine Runbooks match the release candidate.
Product Boss documentation sign-off recorded.
Product Boss release approval recorded separately.

No OBBBA release ships because code alone is complete.

Broader Alpha Gate Still Open

The completed milestone is existing proof-page package migration and live fullInteractive interaction verified. It does not close the full OBBBA Discourse-to-Astro Alpha gate.

Fresh topics and pages must still prove:

Section 10102/topic 747: import with no hero and no pruning.
Section 10103/topic 751: hero placement only, with required alt text.
Section 10104/topic 752: prune rules only, verified locally.
Section 10105/topic 753: hero plus prune rules, verified locally.
Each generated page has discussionSourceMode: discourse-imported, discussionSync: false, and the correct topic ID and URL.
Each approved proof builds, deploys, renders live, and displays comments.
No proof accidentally writes imported Astro content back to Discourse.

The Alpha gate also requires a usable import discovery/queue:

Curated explicit-topic or manifest imports preserve operator order.
Category selection lists available categories and subcategories and accepts category ID or an unambiguous slug/name.
After category selection and preview, “next” selects oldest created_at first, with topic ID as the stable tie-breaker.
Tags, created-date range, open/closed status, and limit filters can be applied where needed.
Oldest/newest ordering uses created_at only.
Candidates are previewed and already imported topics are excluded.
Replies and activity never reorder the queue; bumped_at, last reply, and latest activity are prohibited sequencing inputs.