Skip to content

v1.21.0

Choose a tag to compare

@jadenblack jadenblack released this 16 Nov 13:45
· 49 commits to main since this release
Immutable release. Only release title and notes can be modified.
8add4d7

[1.21.0] - 2026-11-16

Added

  • feat(demo) — #1081 — seed the admin half so the console rail is not empty states (#1104)
  • feat(model) — a draft session is not a live session — state draft -> active at acceptance (#1100b) (#1105)
  • feat(model) — session_invite gains relationship_id, backfilled (#1100a) (#1101)
  • feat(config) — one env manifest, generated .env files, and a no-secret gate check (#1088) (#1089)
  • feat(demo) — #1079 the demo dataset spans the whole relationship lifecycle (#1083)

Fixed

  • fix(templates) — make the catalogue and the create route one set, and import the templates additively (#1099) (#1102)
  • fix(demo) — preserve the pre-reset state with the restore, not before it (#1098)
  • fix(demo) — retry the trusted-origin step on 5xx and restore the pre-reset state when it cannot converge (#1091)
  • fix(demo) — the demo holds 2 subscriptions, not 1 — one row per plan-initiating demo account, and the number is now computed (#1090)
  • fix(billing) — pin Stripe-Version, resolve Prices by lookup key, and run test-mode only (#1085)
  • fix(demo) — re-apply the branch's trusted origin in demo:reset, and prove sign-in (#1086)
  • fix(demo) — #1083 left the seed reading a field it deleted — pnpm demo:reset emptied the branch (#1087)
  • fix(db) — the seed proves every admin seat can sign in (#1080) (#1082)
  • fix(flow) — #975 D8/D13 — stage 1 refuses in words, and the rail stops offering Logout to a visitor (#1078)
  • fix(dashboard) — a payment opened from a relationship stays on the dashboard, and Cancel returns to it (#975 D10) (#1076)
  • fix(flow) — a never-sent draft is no longer an invited assessment (#975, D6) (#1077)
  • fix(docs) — one file scope for the md-normalise snapshot and its test (#1073) (#1074)
  • fix(gate) — stage5-send-live writes the row the send actually reads (#1069) (#1071)

Maintenance

  • chore(admin) — make /admin/growth URL-only — drop the nav row, keep the page (#1095) (#1097)
  • chore(qa) — #1094 demote the QA atlas — drop qa:atlas:check from the gate, defer all sweeps, delete nothing (#1096)
  • docs(readme) — rewrite README for the AlignSynch build only (#1092) (#1093)
  • docs(ux) — #975 every row names a card or a declared deferral (#975) (#1075)
  • docs(ux) — #975 the inventory lands in the tree, and every row names its commit or says uncarded (#1047)
  • chore(repo) — #683 — a repeatable worktree prune, with the squash witness ancestry cannot see (#1046)
  • ci(release) — pnpm release:cut computes the number, refuses disagreement, and is the only tag path (#1064) (#1065)
  • chore(health) — re-record platform health at v1.20.1 (#1072)

Known limits

  • A draft session is not a live session, and session.state defaults to active. The row exists
    from the Initiator's commit — it is the only home for mode, the Setting, aspects_authored_at and
    the Initiator's own seat — so a session's presence is not evidence that anybody joined. draft
    means the relationship has no Counterparty seat; lib/flow/store.ts::claimInvite is the one write
    that flips it, and a draft session is counted by none of the dashboard's three filters and reads as
    a draft rather than as a session with no answers. The column's default is active
    (db/migrations/0041_session_state.sql), because every row older than that file was written by a
    create that opened a session for a pair, so the backfill corrects only the rows the seat rule can
    see — a row written by a path that does not set the column is live by default.

  • Production's schema is two migrations behind the code it already serves. Production's
    schema_migrations ledger names db/migrations/0039_session_aspects_authored_at.sql as its newest
    entry and its session table carries no state column, while https://alignsynch.com/api/version answers
    {"version":"1.20.1","commit":"1ce29064"} — this release's own base, whose create and acceptance
    paths write that column (lib/flow/store.ts::createInstanceFromTemplate inserts state = 'draft',
    and the claim flips it to active). So the next create or acceptance on production writes a column
    the table does not have until somebody runs pnpm db:migrate against production deliberately. No
    gate step can see this: CI has no connection string, and pnpm build has no database.

  • The noun sweep is not in this release. instance → session in the code (issue #1103 phase 2,
    PR #1106) and the bundle format's version 3 (phase 3, PR #1107) are open and DIRTY against
    main, deferred to v1.22.0; content/bundle.ts still declares bundleVersion: 2. Both nouns are
    therefore still in the tree, the code comments and parts of the docs, and a bundle exported today
    is a version-2 document.

  • No dependency majors. #1027 (swiper 14.4.0) and #1025 (jsdom 31.0.0) are open and are
    not in this version — both deferred to the v2.0 sweep. package.json still resolves ^12.2.0 and
    ^30.1.3, so no dependency moved in this window.

  • Production's two ADMIN_EMAILS seats still answer 401. walt1@alignsynch.com and
    alignsynch@riolabs.ai return INVALID_EMAIL_OR_PASSWORD against https://alignsynch.com
    (#1084). That is an existing limit, not a regression: #1080 measured it on the demo branch and
    #1082 provisioned both seats there, in the seed and across a reseed; production has no equivalent
    and this release adds none.

  • The demo dataset is a demo-branch dataset. #1083 and #1104 make the seed author every stage
    of the relationship lifecycle and the admin half of the console, and they are gated on DEMO_AUTH
    inside the seed — so production carries its own rows, not these. A reader comparing the demo host
    with alignsynch.com is comparing two datasets, and the counts will not agree.