Tags give the ability to mark specific points in history as being important
-
pre-function-runner-removal
11ec5938 · ·Baseline before removing Function Runner and the workflow chain editor (2026-08-27). Last commit with workflows-core/workflows-react and the FR integration intact.
-
pre-design-sync
5781302e · ·Restore point taken immediately before running a design-sync `beta/main` as it stood before a Claude Design sync was run against it. A sync regenerates the token/design layer, so this is the state to compare against or return to if it lands something unwanted. At this commit: both theme-review passes plus the merged conduit in-memory-new-request work. Verified green here — tsc across all packages, the full unit suite, eslint, oxlint at zero errors, and the app driven in a browser in all four themes.
-
pre-theme-review
c5244634 · ·Baseline — before ANY Spectrum theme-review work The last commit before the design-language passes began. Everything the review touched (`ui/docs/theme-review/README.md`) is downstream of this point. Reverting the design language ENTIRELY means going here — but note this is also before the conduit in-memory-new-request work, which is unrelated and was merged in later. To drop the design language while KEEPING that, revert the range pre-theme-review..theme-review-full-scope rather than resetting to this tag. What is downstream of here, in order: theme-review-color-only colour/token pass (no layout) theme-review-full-scope + the layout pass (merge) + 33 commits of conduit work from the other checkout
-
theme-review-full-scope
c5747b56 · ·Spectrum theme review — BOTH passes complete, before the conduit merge The end of the design-language work and nothing else: colour/token pass plus the layout pass, with no other feature work mixed in. `main` moved past this when the conduit in-memory-new-request branch was merged, and the `theme-review/full-scope-with-layout` BRANCH was moved onto that merge, so this tag is the only name for the clean boundary. This is the useful handle for a design-language revert: git revert --no-commit pre-theme-review..theme-review-full-scope drops the design work while leaving the conduit work intact, because the two never interleave — they meet only at the merge commit. Contents, over `pre-theme-review`: 16 commits, ~76 files. core-react (tokens, theme layer, table, chip, card selector), jiggleranch-react (kanban, queue, job card), demo-react (explore, nav, screenshot harness), plus both CLAUDE.md palette tables. Scope of each pass is recorded on `theme-review-color-only` and in ui/docs/theme-review/PASS-2-SCOPE.md.
-
theme-review-color-only
ee929dfe · ·Spectrum theme review — the COLOUR/TOKEN pass only Scope marker for the work in c5244634..ee929dfe, implementing ui/docs/theme-review/README.md. Deliberately bounded: this pass changed the DESIGN LANGUAGE (colour, tokens, type roles, surfaces) and did NOT change layout, spacing, or which controls exist. IN SCOPE — done §9 theme layer is token-only; no component branches on theme, no [data-spectrum=…] [data-slot=…] rules. New tokens: --color-control, --color-table-header, --color-card-border, --color-primary-ink, --table-header-transform/-tracking, --title-*, --chip-*, --button-solid-shadow, --button-text-affix, --gradient-header. §1 accent spent on selection only, not on all sixteen rail icons §2 rail rows are rows, not cards (CardSelector `rail` mode) §3 semantic colours off non-semantic actions (Refresh/Reset/queue badge) §4 Signal's hairline containment, via --color-control (Signal-only) §5 table header hierarchy; numerics right-aligned, mono, tabular-nums §6 surface sequencing — no dark/light banding down the page §7 header wash as one token; the mark moved off the action buttons §8 kanban/state colours come from tokens (were hardcoded hex, so all four themes looked identical below the page header); status mark reshaped circle -> square so it stops colliding with the avatar shape §10 Ember retuned — leather + brass replacing cocoa + clay §11 Daylight retuned — surface ladder + split accent (fills vs text) §12 Graphite left on MUI's terms, deliberately not corrected toward Signal §13 the two component defects (properties divider, undefined timestamps) plus the dialog's flat rail/content/footer §14 tab label case; the rest of §14 was already correct OUT OF SCOPE — NOT done, by instruction ("mockups may move or remove buttons; you do not need to do that") - hover-revealing the per-row and per-card action icons (§5, §8, §13) - kanban card tightening / full-height columns / docked `done` rail (§8) - the label-vs-numeric column width inversion (§5) - any spacing, padding, or density change - §8's user-chosen-colour subsection, marked FOLLOW-ON in the review LEFT FOR A DECISION, not silently taken - §13 wants the preview dialog on the `overlay` tier; CLAUDE.md explicitly forbids that for this dialog ("a page in a box"). The inner three-step frame was done; the surface was not moved. - v1/Graphite's on-accent (white on #2196f3) is 3.12:1, below AA and inconsistent with the repo's own getContrastText(). Pinned by a named test rather than changed — it recolours every filled primary control in the default theme. - user-set state colours (StateNodeConfig.color) still never reach the kanban lanes or chips; those call the name-based fallback directly. That gap predates this work and is the §8 follow-on. Two deliberate deviations from the mockups, both for contrast, both documented in fe603c5c: Daylight's accent text (#b23a27, not #c4442f) and its on-accent ink (dark, not near-white). Verified: pnpm -r run tsc, all unit tests, eslint + oxlint, and the app driven in a browser in both Ember and Graphite. -
pre-kanban-new-request
7c53c35a · ·Last commit before the kanban-new-request refactor (nav Conduit→Requests merge); next commit dbe4f7e7 starts the mockup
-
pre-chat-virtualization
32945a46 · ·Last commit before chat panel virtualization work. Rollback point: origin/main as of 2026-06-16, immediately before the chat-virtualization branch (spec dcb2b88 onward). Reset to this tag to revert all virtualization changes.
-