Epic: promote develop to main so the demo and hosted app show current code #555

What this is about

People can see DeltaTrack in two public places:

• The hosted app at https://deltatrack.agoradmv.org/. You upload two versions of a bill and get a comparison report.
• The example reports, which serve as the demo. These are static pages published with GitHub Pages and linked from the README under "See it in action".

Day-to-day work is merged into the develop branch. Neither public surface is built from develop; both are built from main. Moving develop's work onto main is called a promotion. It is a pull request from develop into main that a maintainer opens and merges. The step-by-step runbook is docs/release.md.

What's wrong

The last promotion was #603, on 2026-08-11. Here is what has happened since (measured 2026-10-05):

• develop is 513 commits ahead of main.
• The example reports haven't been republished since 2026-08-11. Pages only publishes when main changes. They still show August's output, and they were published before the repository moved from the AgoraDMV organization to civictechdc.
• main's README links the demo at the old agoradmv.github.io/DeltaTrack/ address. develop's README already uses civictechdc.github.io/DeltaTrack/.
• The hosted app is now frozen until the next promotion. It used to redeploy on every push to develop. On 2026-10-04, .github/workflows/deploy.yml was changed to deploy only from main. So the app stays on develop as of 2026-10-04 (commit ee9aeb6) until the next promotion.

Why it matters

Anyone who follows the README sees output from August's renderer, without two months of fixes. The gap grows with every merge to develop.

The next promotion also runs two things for the first time:

1. The app deploy triggered by a push to main. The deploy workflow (named "delivery" in the Actions tab) has run 11 times, all from develop. Its credentials work, since those runs succeeded, but it has never been triggered by main.
2. The first Pages publish from the civictechdc organization. It is unverified whether the repository's Pages settings survived the transfer.

Neither of these can be tested from a pull request. Both run only after the merge to main.

Sub-issues

Done when

• A promotion pull request from develop to main is merged, following docs/release.md.
• All four workflows that run after the merge succeed on main: CI, security, Publish examples and delivery.
• https://civictechdc.github.io/DeltaTrack/ serves the reports currently in examples/, and every "See it in action" link in the README resolves.
• One real comparison runs on the hosted app after it is deployed from main.
• Anything that broke is written into docs/release.md or docs/deployment.md, so the next promotion isn't a first attempt.

Scope

• In scope: the next promotion, and recording what it teaches.
• Out of scope:
  • How often to promote. That's a team decision.
  • How the app runs once deployed: rate limits, scaling, memory.

Where to start

• Before you begin: opening the promotion pull request is the maintainer's call (see the top of docs/release.md). A contributor can help by working on Before the next promotion, confirm the Pages settings survived the move to civictechdc #556, or by reading the two workflows below against the runbook and reporting anything that looks wrong.
• What to read:
  • docs/release.md: the promotion steps and how to roll back.
  • docs/deployment.md: what the app deploy does and what the host needs.
  • .github/workflows/deploy.yml (the app) and .github/workflows/update-examples.yml (the example reports).