Skip to content

Deploy to PROD 11/19/26 - #2381

Merged
Mephistic merged 17 commits into
prodfrom
main
Nov 19, 2026
Merged

Mephistic merged 17 commits into
prodfrom
main

Conversation

@Mephistic

Copy link
Copy Markdown
Collaborator

Changelog

Extra Deploy Steps

dasanchez and others added 17 commits November 16, 2026 11:28
Conference committees: Follow and see new input in the newsfeed and the email digest
…slators (#2359)

* Send conference letters and updates from their own subdomains

Letters to legislators now come from noreply@letters.mapletestimony.org
and the weekly update to conferees from noreply@updates.mapletestimony.org,
on dev and prod, instead of notifications@. Each stream keeps its own
sender reputation, apart from the other and from the digests on the main
domain. Merge only after SendGrid has verified both subdomains, since it
rejects mail from a sender domain it has not authenticated.

Not verified: a send from either address; the subdomains' DNS was not
live, so SendGrid has not verified either yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Compile each conference's weekly update from its input

A trigger on published testimony records each add, edit and withdrawal of
conference input in conferenceInputEvents, kept apart from
notificationEvents so the digest never sees them. On Mondays at 8:00
Eastern a job reads the previous Monday-to-Sunday window of events for the
net change, reads the conference's live input for where it stands, renders
the email HTML, and creates conferenceUpdates/{court}_{id}_{week}. A week
with no change stores nothing, and a second run leaves the first update as
it was. All conference input counts; an admin deletion counts as a
withdrawal. The update has no number and no unsubscribe line, and follows
the designer's mockup without its open-questions section and form.

The conference stance wording moves to shared/conferences so the digest
and the update use one copy.

Closes hyphacoop#137

Verified: functions jest and the conference component tests (119) pass;
the integration cases "conference weekly update" pass on a throwaway
emulator with the opt-in removed: the trigger, a callable edit, an admin
deletion, the job, an idempotent rerun and an empty week; functions and
website type checks pass apart from untracked scratch scripts under
scripts/firebase-admin.

Not verified: the HTML was laid beside the mockup before two lines of its
wording changed (the footer, and the note under "Read the testimony"); how
it renders in real mail clients; a full run of the integration file; the
job on a deployed schedule. "Read the testimony" links the conference page
without a total because Public Input has no date filter.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Email each conference's weekly update to its conferees

The job that compiles a conference's update now also queues its email, in
the same batch that stores the update, so a second run in the week finds the
update and sends nothing. The email goes out from MAPLE with replies to
info@ and a SendGrid category for the update, set in the document's
top-level headers: the send-email extension ignores message.headers. The
update records which conferees it went to and which were skipped for having
no email address.

Outside production no email reaches a legislator: the To line becomes
LETTER_TEST_RECIPIENT and the subject names who it would have gone to. With
no test address set, nothing is sent. The sending address comes from
CONFEREE_UPDATE_FROM and defaults to notifications@ until the updates
subdomain is authenticated.

Closes hyphacoop#138

Verified: functions jest (176); integration "conference weekly update" on a
throwaway emulator: swapped recipient and subject prefix, headers, replyTo,
no second email on rerun, real addresses in production mode, skipped
conferee without an address, update stored with no email when none has one;
that extension 0.1.36 reads headers from the top level of the document, from
its source; a run on the local emulator with the send-email extension sent
an update through SendGrid that reached the test inbox.

Not verified: the SendGrid category arriving; the sending address on the
updates subdomain, which waits on hyphacoop#140.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Show readers where their conference input goes, and preview their letter

The review step before posting new conference input or a cosign now says
where it goes (public on MAPLE, emailed to the reader's own rep and
senator, counted in the weekly update), shows the letter as it will be
sent with a Cc row, and lets the reader give a different reply-to for that
letter alone. A cosign gains a review step after writing; a cosign without
a note gets the mockup's "add a line" banner. A reader whose profile has no
rep or senator is told MAPLE has no one to notify, and sees no letter.

The reply-to is kept on the reader's private draft and never copied to the
publication. The letter text comes from one pure renderer under
functions/src, so the daily sender can mail exactly what was previewed.

Closes hyphacoop#142

Verified: yarn test:website, yarn test, check-types, lint on the changed
files and yarn build:dev pass. A throwaway-emulator integration test shows the reply-to stays
on the draft and is absent from the publication. The review blocks were laid
beside the mockup's Review frame at panel width.

Not verified: phone width, and the review flow in the real panel with a
signed-in reader on the emulator. The cosign screens were not laid beside
their mockup frames.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Mail each new conference input to the reader's rep and senator

A daily job reads the previous Eastern day's newly added conference input
and writes one email per letter, using the same renderer as the review
step's preview, to whichever of the reader's rep and senator has an
address. The reader is copied and replies go to the address they chose for
that letter, else their verified one. The email is created under the input
event's id, so a rerun sends nothing twice, and an input posted twice in a
day sends only its last. Inputs that are not mailed are recorded with the
reason. Outside production recipients are swapped for the test address.

Tracking headers go in the email document's top-level headers: the
send-email extension ignores message.headers.

Closes hyphacoop#143

Verified: unit tests for the day window, From header and email document;
an integration test on a throwaway emulator covering a sent letter, rerun,
reply-to override, a legislator without an address, each skip reason, and
a repost; input posted through the review step on the local emulator
was mailed through the send-email extension and SendGrid and reached the
test inbox, copying the reader.

Not verified: the letter's look beside the mockup, and DKIM and DMARC from
the letters subdomain.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Write the letters' and weekly updates' plain text from their content

The text part of each email was the HTML's textContent, which drops
line breaks: a letter's signature ran together ("Fake VioletHouse
district: 12th Suffolk...") and the update's figures ran into their
labels. Each is now rendered from the same data as its HTML, with a
line per signature line or figure and the cosigned input quoted.

Verified: letter and update unit tests (36) and functions tsc pass; a
letter and two weekly updates sent through the local emulator's
send-email extension and SendGrid arrived with readable text parts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Run the conference mail jobs once against the local emulators

The emulators never fire schedules, so a new admin script runs the
letters or weekly-update job as its next scheduled run would, or at a
given --now. It is local only, and mails LETTER_TEST_RECIPIENT as read
from the functions env files. The README says how to start the
emulators with the send-email extension, and the extension's local
secret file is ignored.

Verified: with the extension emulator and a SendGrid key, letters and
updates runs reached the test inbox; the only recipients were the test
address and the reader's reply-to, with legislators named only in the
subject; a bad --job is refused with the usual arguments error.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Mail edits to conference input as updated letters

An edit to posted conference input now mails a new letter, its subject
marked "(updated)" unless the input was also first posted in the same
day's run; the preview shows the same subject while editing. The letter's
footer links the conference's page rather than nothing. The draft holding
the reply-to is found by court as well as conference, and a reply-to that
is not a single address is refused on the draft and ignored by the sender,
which falls back to the reader's verified email. The conference's name
comes from one helper in functions/src/shared.

Verified: functions jest (letter, letters, testimony); yarn test:website
conference tests (128); check-types; lint; integration conferenceLetters
and testimony on a throwaway emulator (edit mailed as update, post and
edit the same day mailed once as new, conference link).

Not verified: yarn build:dev. An edit whose original letter was skipped is
still marked "(updated)"; a same-day post and edit previews "(updated)" but
sends without it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Count a weekly update's changes up to when it is compiled

The update's changes ran Monday 00:00 to Monday 00:00 but the job runs at
8:00, so input in those eight hours waited a week. They now run from a week
before the compile to the compile. The update keeps the Monday it is named
for in its id, weekStart and heading. A Monday run that fails and is rerun
later in the week misses or repeats about a day of changes.

Verified: functions jest (weekWindow across the week and daylight saving);
integration testimony.test.ts on a throwaway emulator.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Mail each conference input at the first 9:00 after it's posted

The daily letter job ran at 9:00 Eastern but mailed the previous calendar
day, so input posted before 9:00 waited a day, and a post at 23:00 edited
at 8:00 was mailed twice. The day's window now runs from the run a day
before to this one, as the weekly update's does, stepping back a calendar
day so the windows meet at 9:00 across clock changes.

Both scheduled jobs now take the time the run was due from the scheduler,
not the time it started, so each window begins exactly where the last one
ended. The jobs take that time as a required argument, and the local
run-once script runs the letters as of now.

Closes hyphacoop#145

Verified: dayWindow tests for the 9:00-to-9:00 window, input posted at
00:30 mailed that morning, and both clock changes; functions jest for
conferenceLetters and conferenceUpdates (38); check-types, functions tsc,
lint and prettier; the conferenceLetters integration test (10/10) on a
throwaway emulator with a Typesense stand-in, before now became required.

Not verified: a real scheduled run passing scheduleTime; the testimony
integration test's weekly update cases; yarn build:dev.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Record every email MAPLE sends to a legislator

Each letter and weekly conference update is now recorded at
/legislatorMail under its /emails document's id, created in the same
batch, so neither exists without the other and a rerun adds nothing.
The record keeps the kind, court, the legislators' member codes (the real
ones outside production), the subject as they see it and the body; a
letter adds the reader, testimony, version, conference and whether it
went out as an update, and an update adds its week, standing and changes.
It replaces /conferenceUpdates, so an update no conferee can receive is
no longer stored. Readers can read the records of their own letters.

Closes hyphacoop#146

Verified: conferenceLetters and testimony integration suites (89) on a
throwaway emulator with a Typesense stub, including records, reruns and
the read rule; functions jest for conference letters, updates and email;
check-types, functions tsc, lint, build:dev.

Not verified: the composite index deploys; a real scheduled run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Decide repeat and updated letters from the record of what was sent

The letter job decided whether an edit was an update from the events in
its own run, so a version already mailed could go out again and an edit
could be marked "(updated)" after an original that was never sent. It now
reads /legislatorMail: an event whose own letter is on record is done, an
input whose current version already has a letter is skipped with the new
reason alreadySent, and a letter is an update only when an earlier one
for that input is on record. The reader's preview asks the same question
of their own records, so its subject matches the letter that is sent.

Closes hyphacoop#147

Verified: conferenceLetters and testimony integration suites (92) on a
throwaway emulator with a Typesense stub, including each version mailed
once, an edit after a skipped original going out unmarked, an edit after
a sent letter marked updated, and the preview's query under the read rule;
InputForm and CosignForm tests for the preview's subject; functions jest
for conference letters, updates and email; test:website, check-types,
lint, build:dev.

Not verified: the preview in a running site; the preview's two-field
query against real Firestore indexes; a real scheduled run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Mail conference input by when its event was recorded

The letter and weekly update jobs read the events whose publication was
written in their window, but the trigger records an event after that
write, sometimes after the run has read the window. Such an event was in
no window: no letter, no skip, missing from the update. Events now carry
recordedAt, the time the event itself was written, and both jobs read by
it, so a late event goes out with the next run. The trigger creates the
event, so a second delivery keeps the first time.

A letter or update that fails now fails the run after the others, and
the schedules retry it; what was sent or skipped is created by id, so a
retry repeats nothing. An event already mailed or skipped is left alone
on any later run, read once for the window, so a rerun no longer records
a mailed event as superseded and a skip is final.

Verified: conferenceLetters and testimony integration (94) on a
throwaway emulator with a Typesense stub, including an edit recorded
just after a run going out on the next, and a rerun after a later edit
leaving the first letter alone; functions jest for conference letters,
updates and email; functions tsc, check-types, lint, formatting.

Not verified: a run failing and being retried; that a retried run gets
the original scheduleTime from Cloud Scheduler; a real scheduled run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Send cosign edits through the letter review

Editing a posted cosign mailed the legislators an updated letter the
reader never previewed: the edit posted straight from its note screen.
Both forms now end at one review step, with the letter preview, the
reason for the change and the post rule (changed, and a reason when
editing) worked out in one place. The write screens stay separate, as
the mockup draws them. The panel keeps one step state for both.

Posting an edit also clears the form's reason, so the next edit no
longer starts with the last one's.

Closes hyphacoop#148

Verified: test:website (296), check-types, lint, formatting. On the
local stack: a cosign edit goes write, review, post with a reason
required; after the letter job mailed it, the next edit previews
"(updated)"; the next edit's reason is empty; the cosign review stacks
at about 560px.
Not verified: build:dev (the dev server held .next); exactly 390px;
the review laid beside the mockup's compose review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Refuse to run the integration tests without Typesense

The functions sync every testimony and bill write to Typesense, which CI
runs as a service. Without it locally, each sync threw, the emulator
killed that function's worker, and every later event waited on a cold
start; the backlog timed out triggers the tests wait on, the cosign tally
most often. The runner now checks the TYPESENSE_API_URL in the demo
project's env file and stops with the command to start it.

Verified: without Typesense, 160 worker loads and tally timeouts; with a
stand-in answering on 8108, 16 loads and testimony plus conferenceLetters
pass (88/88); the runner stops with its message when nothing answers.

Not verified: a full run against a real Typesense container.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Matt gets test emails in dev.

* Send replies and the copy to the reader's own email

A letter's Reply-To, Cc and signature line were the address the reader
chose for that letter, kept on their private draft. They are now always the
reader's verified account email. The review step shows that address
instead of offering another, and the sender no longer reads the draft.

Verified: functions jest, test:website, check-types, eslint on the changed
files, integration tests for conferenceLetters and testimony on a throwaway
emulator, and build:dev.

Not verified: the review step in a browser on the local stack.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Word conference input as "Pass a final bill", per the design

The designer's mockup renames "Please pass something" to "Pass a final
bill", which covers readers who want any law and readers asking for a
specific provision, and "Don't pass anything" to "Don’t pass a final
bill". Site and email labels change together; the stored position keys
stay, so nothing migrates. Chips and the filter read "Final bill" and
"No final bill".

The input panel's prompt now follows the chosen position, the two broad
positions say what they mean, and a note under the field says where the
input goes. Panel titles name the step (Review Your Input, Cosign Input,
Review Your Cosign), the weekly-update rows say "six conferees", the
cosign field reads "Add a line of your own (optional)" with where the
line lands, and its button "Review and Cosign". The review step drops
"Before You Post", which the design has none of. The mockup's
weekly-update and how-cosigning-works links stay plain text: there is
no page for either yet.

Verified: yarn test, yarn test:website, yarn check-types, lint; local
stack walk of Add Your Input (help lines, per-position
prompts, delivery note), Review Your Input, Cosign Input and Review Your
Cosign without a line, including at 390px.
Not verified: the email preview in the panel (the seeded user has no rep
or senator); tests/integration/conferenceLetters.test.ts subject
expectations were updated but not run; yarn build:dev passed only
before the last styling cleanup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Invite readers without legislators on file to add them to their profile

The note under the input field promised an email to the reader's
representative and senator even when their profile has neither, and the
review step then said nobody would be emailed. Without legislators the
note now promises only the weekly update to the conferees and links to
the profile page to add them.

Verified: the InputForm test suite passes, including both note variants.

Not verified: the link and its wording in a browser; the copy is not in
the design and needs the designer's sign-off. check-types and
test:website were not run.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Added a Design Tokens story and a switchable Digital Democracy skin

* experimenting with hero and calmatters theme

* component picker, account type in testimony page, background art, new logo, various style fixes, rework footer and create component

* clean up components

* touch up leg profiles to use our components, touch up lobbying banner. align learn and about breadcrumbs to match leg profiles

* add variables to be able to create demo link

* fix some responsiveness items

* fix a few style bugs, and address screens once a user is logged in

* Show only the Statehouse design and remove the skin switcher

The branch carried four skins behind a dev switcher (Maple, Digital
Democracy, Mixed and Statehouse), and only builds with the switcher could
show Statehouse. The page itself set the Digital Democracy theme, so a
production build showed plain Digital Democracy instead.

Set the redesign on every page in _document.tsx and keep only what
Statehouse showed, with the explorers' background art off. Remove the
switcher and the Maple, Mixed and plain Digital Democracy branches from
components and CSS, along with the page art, the section ground, the
search panel hero, the legacy hero, their stories and images, and the copy
only they used. Options that are now always on (the legislator picker's,
the verify account card's) become the components' only behaviour.
Storybook renders the same design with no skin menu, and comments describe
the one design.

* Add filter testimony by author type in the tests, and drop the hidden tabs

* Flatten the redesign's styles and drop the hidden skyline slices. Write the redesign's rules under :root (*:root in styled-components). Remove the attribute from the page and Storybook.

* tidy some lobbying explorer components to fit in storybook design

* Ran an AI code and accessibility review that caught a few findings.

A review of the branch found places where the redesign broke keyboard and
screen reader access, a test that no longer matched the page, uneven
spacing, and code left over from the themed experiment.

- Edit Profile: put the four tabs in one tab list so the arrow keys reach
  them all, and make the card band titles headings.
- Testimony explorer: name the Author Type radios as a group.
- Follow button: mark it as a pressed toggle while following.
- Conference Bill Text: darken the empty message to meet AA contrast on
  the grey well.
- Navbar: style Conference Committees by whether the hamburger shows, as
  the other links are, rather than by a 768px width. Give Sign Out the same
  vertical padding as the links above it.
- Homepage: add room under Browse All Testimony on narrow screens so the
  gap before Did You Know? matches the others.
- Profile testimonies: drafts have no bill title until published, so look
  it up instead of showing "Bill Title".
- Lobbying bill page: show each filing's position in its own words, as
  main does, inside the shared chip.
- Footer: use the new white logo.
- Tests: find Browse All Testimony as a link, and expect one conference
  banner again.
- Remove unused colour tokens, a button rule that could never match,
  skyline-mask.svg, dead hero rules, and stale comments.

* clean up sign up modal

* address accessibility issues with menu drawers that the audit didn't catch

* remove stray file from past experiment

* experiment with topic tags

* fix hero height

* rework the testimony cards on the homepage

* new design for testimony on homepage and reorder/clean up home page sections

* fix ordering and link directs. touch up conf comittee legibility

* touch up spacing

* Prepare the redesign for the full reskin deploy

Homepage and site:
- Add the featured area back into the design to showcase MAPLE's new
  features. This is where topics or a search can go in the future
- Fold navbar links into a "Browse More" menu so the bar collapses
  gradually. Matt found it collapsing too soon, a side effect of my fix
  for the nav being too big
- Reorder the footer, with room between its columns so long links wrap
- Redesign the testimony cards to look more professional. I'll come
  back to these, but they are an improvement
- Address comments and bugs found by Matt
- Fix typos in the footer's Instagram link and the homepage's "why"
  section
- Add copy on click to the feedback email with a mailto fallback when
  the browser can't copy
- Change sign in to log in to match the nav button

Lobbying:
- Componentize and standardize the cards across the Lobbying Explorer,
  switching to existing components and creating new ones where needed,
  so every card draws from the same components
- Move a bill's organization filters up beside the panel's title, in
  line with the position column

Conference committees:
- Add a beta banner
- Give Conference Home a page of its own, with each conference on its
  own page and a link back, in place of one page that scrolled between
  them
- Send /conferences/194 to the session's first committee
- Keep the committee list beside each conference from 768px, compact
  below 992px, and as a floating button on phones
- Fold Conference Home's steps and pin its buttons wherever the steps
  stack
- Link the Explorer's narrow list to each committee again, greying out
  the ones we don't cover
- Update the conference tests to the new pages

* Clean up leftovers from the redesign's iterations

- Remove styles for the conference page's old locked mode, an unused
  title width measurement, and options no caller sets
- Remove test stand-ins the conference tests no longer need
- Correct, merge or move comments that were stale, misplaced or unclear

* Make the conference input's type consistent

- Set the input panel and the letter being cosigned in Nunito, as the
  mockup does, keeping Lexend for the panel title and the card's name
- Set names, position and outcome chips, questions and chamber answers
  in Lexend, with names and answers at a lighter weight
- Match the cosign preview to the entry it previews, and raise Public
  Input's text a pixel, with its previews and the cosign letter
- Soften the Cosign button's hover
- Make room for the input panel in the beta banner
- Add a little room to each row of the conference sidebar

* Fix the nav hover height and the feedback email's tips

The nav items' hover shade ran taller than the links need, and the
feedback email showed a "Copy" tip and an underline before it was
pointed at.

- Shorten the nav items' hover to 0.5rem above and below
- Show only "Copied!" on the feedback email, with no "Copy" tip, on the
  homepage and in the beta banners
- Underline the homepage email only on hover, in a light weight

* Change button interaction to match the intent

---------

Co-authored-by: k-g-k <10489124+k-g-k@users.noreply.github.com>
… older courts (#2365)

* adding instructions for ocpf member matching and finance scraping for older courts

* small fixes
* Improve the UX of the providing input panel and cosign panel

* Clean up gray panel

---------

Co-authored-by: k-g-k <10489124+k-g-k@users.noreply.github.com>
#2371)

MAPLE prepares each conference's overview and open questions itself, so
the conference pages now say where that analysis comes from, and their
copy is clearer.

- Subtitle: "Three senators and three representatives are negotiating a
  compromise between the Senate's version (S.####) and the House's version
  (H.####) of <act>. Their report goes back to both chambers for a final
  vote." The counts come from the conferees, spelled out. A conference no
  longer sitting says they "were appointed to negotiate" instead, its
  status saying the rest.
- The section heading is "Overview", the questions sit under an "Open
  questions" label counted like "Where bill texts match", and the tab and
  the list's accessible name say "Open Questions" too.
- The line under the overview is now a disclosure: MAPLE compared the two
  texts with the help of AI tools, reviewed by the team; it isn't an
  official summary; last updated date; the feedback link; and an "About
  this analysis" button that opens a panel in place (aria-expanded,
  aria-controls). The panel's parts are listed in one place,
  ABOUT_THIS_ANALYSIS, with their wording in conferences.json.
- New optional conference field analysisUpdatedAt ("YYYY-MM-DD"), set to
  2026-11-18 on every covered conference, checked by the sync and
  documented in docs/updating-conferences.md. Without it the line leaves
  the date out.


Claude-Session: https://claude.ai/code/session_01D33UhRWMTfqqNcxtGnAz5D

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The House and Senate appointed conferees on H5576 / S3228 on July 30,
2026. Listed like the BRIGHT and Mass Ready Acts: covered: false, so its
page says we haven't written it up and takes no testimony.


Claude-Session: https://claude.ai/code/session_01D33UhQyHRmfcdsVvbKtAwW

Co-authored-by: Matt Victor <mvictor55@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…at (#2373)

The lead and the last three steps say what happens in plainer terms, and
the negotiation step, where MAPLE takes input, is marked "We are here":
its number ringed and a tag beside it, under its title where the steps
stack.


Claude-Session: https://claude.ai/code/session_01D33UhQyHRmfcdsVvbKtAwW

Co-authored-by: Matt Victor <mvictor55@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Conference input and cosigns autosaved as drafts while the reader typed,
and drafts kept going wrong: a hung Post, a cosign's words saved as the
reader's own input, a stale edit reason, saves dropped while the draft
loaded. They also gated the page, hiding Cosign and refusing cosign links
while the reader had unposted words.

Nothing is kept before Post now. Publishing still goes through the draft
document, since publishTestimony publishes a draft by its id, so Post
writes it once, waits for the edit hook to hold it, and publishes.
useAutosave becomes usePost. Both forms start from what the reader
posted, never from a draft, and lose the Saved indicator and Delete
Draft. The page offers Cosign whenever the reader has posted nothing,
and drops the drafting link refusal and the warning about replacing
another cosign's note. Bill testimony is unchanged.

Closes hyphacoop#151

Verified: yarn check-types; lint and Prettier on the changed files;
yarn test:website (44 suites) run inside the dev container. On the
local stack, typing for 4s wrote no draft (emulator query), and Post
overwrote a leftover empty cosign draft as the reader's own input,
published it and landed on it.

Not verified: cosigning, a cosign link and an edit with a reason in the
browser (covered by unit tests only); the panel at phone width; yarn
build:dev.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Disclose the analysis for the whole conference section, not the overview

The AI and curation disclosure read as covering only the overview: it sat
inside the overview's quote box and said "prepared this overview". The
overview, the open questions and the points where the bill texts match are
all MAPLE's analysis, so the disclosure now covers the section:

- It sits at the top of the section, above everything it covers, in its
  own soft grey box with an info mark, in a grey that meets AA contrast
  (the line it replaces was well below it).
- It names all three: "MAPLE wrote the overview, the open questions and
  the points where the bill texts match by comparing the Senate and House
  texts (S.####, H.####), with the help of AI tools and reviewed by our
  team. None of it is an official summary from the Legislature, and it
  may not cover every difference. About this analysis"
- The section is headed "The House and Senate versions", and the
  paragraph has its own "Overview" label, like "Open questions" and
  "Where bill texts match", in place of the grey bar beside it.
- The feedback sentence is gone; feedback is covered elsewhere on the
  site. Corrections in the panel now give info@mapletestimony.org.
- The panel opens with "This is a beta." and ends with "Last updated
  <date>", which no longer sits in the line.
- Enacted conferences, whose section is about how questions were
  resolved, get no disclosure that speaks of open questions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D33UhRWMTfqqNcxtGnAz5D

* Set the overview in the open questions' column

The overview was capped at 90 characters a line, a width tied to nothing
around it: on a wide screen it ended about 100px past the open questions'
column, partway into the gap before the matches. It now sits in the same
column as the open questions, so its lines end where theirs do, and it
still takes the full width where the columns stack. Its label is as far
above it as the open questions' label is above them (12px).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D33UhRWMTfqqNcxtGnAz5D

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The notice on an uncovered conference's page now says why: it's a bond
bill, long, heavily amended and unlike the other bills in conference, so
MAPLE lists who's negotiating and both versions but takes no input, and
is working on features to cover them. A short italic note under the rail,
and under the mobile picker's lists, says the same wherever one of these
is listed.


Claude-Session: https://claude.ai/code/session_01D33UhQyHRmfcdsVvbKtAwW

Co-authored-by: Matt Victor <mvictor55@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Support MAPLE page: lead with donating, open checkout on MAPLE

- Donate is now the first card, with a one-time/monthly switch, suggested
  amounts and a Donate button that opens the Fundraise Up checkout for the
  "General Donations - MAPLE" campaign over this page, instead of sending
  donors to the Partners in Democracy site. Fundraise Up's installation code
  loads on this page only. If it is blocked, the button and a fallback link
  go to the same campaign on PiD's site.
- Use, Volunteer and Feedback become a row of "Other ways to help" cards.
- Drop the separate bug report form; the feedback card points to the one
  feedback form and asks people to say which page was broken.
- Subhead now says MAPLE is a project of PiD – Education, a 501(c)(3),
  instead of calling MAPLE itself a nonprofit.
- Page copy moves into public/locales/en/supportmaple.json; remove the
  unused SupportMapleCardContent component.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D33UhPdUn8Ta2UKiKr3VRe

* Support MAPLE page: tighten the case for giving, list what gifts pay for

Replace the two paragraphs beside the give box with one shorter one and a
"Your gift pays for" list (free access, hard-to-find information, what
comes next), so the text column fills the space beside the give box.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D33UhPdUn8Ta2UKiKr3VRe

* Support MAPLE page: say "conference committee deep dives"

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D33UhPdUn8Ta2UKiKr3VRe

---------

Co-authored-by: Matt Victor <matt@partnersindemocracy.us>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A second review of the nine conferences still in conference, checking each
answer against both bill texts and, where it depends on it, the law being
amended.

- Shorter overviews: the purpose and the main differences.
- Open questions and points of agreement chosen, reordered and corrected
  where an answer presented current law as new or misread a chamber's text.
- Points of agreement written as plain statements, each with a short
  explanation.
- State-law citations in the enacted pages' style ("G.L. c. 55 §1").
  Teacher Benefits' Senate citations name subsections, since that bill has
  no numbered sections.
- Straight quotes, AP-style dates, and "Not in the bill" where the Senate
  public records bill is silent on fees.
- "Where bill texts match" is now "Where the bills agree".
- "About this analysis": "What we read" names the laws the bills would
  change and related bills and ballot questions; "How it's written" says
  each question and answer is checked against both bill texts and, where an
  answer depends on it, the law being amended.
- analysisUpdatedAt is 2026-11-19 on the nine.


Claude-Session: https://claude.ai/code/session_01D33UhRWMTfqqNcxtGnAz5D

Co-authored-by: Claude <noreply@anthropic.com>
* Add link-preview tags support and site URL constant

* Add newsletter signup component

* Add /newsletter page

* Add newsletter page text

* Add newsletter share image
* layout and mobile changes

* Improvements to the input panel

Removed the weekly email tab and fixed the panel layout bugs. The
committee page was sized by the window, which created all sorts of
issues. Plus small UI tweaks.

* Improvements to conference explorer

* Fixed no-input cosign text and display, the loader buttons on submit, and missing action bar. Addressed other UX bugs in the public input list, input cards and cosigns, input form, and more layout tweaks. Also changed the style of how your own posts appear.

* Updated conference home, sidebar groups, tabs from card titles and explorer table

* Removed the org review message

* Hide hearings for now

* Fix overview and make text color and sizing consistent

* Show cosigns without content by default and add minor cosign display control

---------

Co-authored-by: k-g-k <10489124+k-g-k@users.noreply.github.com>
@vercel

vercel Bot commented Nov 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
maple-dev Ready Ready Preview Nov 19, 2026 6:35pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
maple-prod Ignored Ignored Nov 19, 2026 6:35pm UTC

Request Review

@Mephistic
Mephistic merged commit c915391 into prod Nov 19, 2026
11 of 12 checks passed

This branch was successfully deployed

1 active deployment
Production – maple-dev — 2714939e Deployed Nov 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants