savepoint 1.0.0

package/internal/styles/styles.go

@@ -0,0 +1,122 @@
+package styles
+
+import "github.com/charmbracelet/lipgloss"
+
+func color(hex, ansi256, ansi string) lipgloss.CompleteColor {
+	return lipgloss.CompleteColor{TrueColor: hex, ANSI256: ansi256, ANSI: ansi}
+}
+
+var (
+	clrOrange      = color(AtariOrange, AtariOrange256, AtariOrange16)
+	clrText        = color(PrimaryText, PrimaryText256, PrimaryText16)
+	clrBorder      = color(BorderSubtle, BorderSubtle256, BorderSubtle16)
+	clrSurface     = color(Surface2, Surface2256, Surface216) // #0F0F0F
+	clrSurfaceDark = color(Surface, Surface256, Surface16)    // #0D0D0D
+	clrGreen       = color(NPPGreen, NPPGreen256, NPPGreen16)
+	clrPurple      = color(VibePurple, VibePurple256, VibePurple16)
+	clrDim         = color(Dim, Dim256, Dim16)
+)
+
+var (
+	HeaderIcon = lipgloss.NewStyle().
+			Foreground(clrOrange).
+			Bold(true)
+
+	HeaderText = lipgloss.NewStyle().
+			Foreground(clrText)
+
+	Divider = lipgloss.NewStyle().
+		Foreground(clrBorder)
+
+	HeaderFrame = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrBorder).
+			Padding(1, 1)
+
+	BoardFrame = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrBorder).
+			Padding(0, 1)
+
+	Column = lipgloss.NewStyle().
+		BorderStyle(lipgloss.RoundedBorder()).
+		BorderForeground(clrBorder).
+		Background(clrSurfaceDark).
+		Padding(0, 1)
+
+	ColumnFocused = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrOrange).
+			Background(clrSurfaceDark).
+			Padding(0, 1)
+
+	ColumnTitle = lipgloss.NewStyle().
+			Foreground(clrText).
+			Bold(true)
+
+	ColumnTitleFocused = lipgloss.NewStyle().
+				Foreground(clrOrange).
+				Bold(true)
+
+	TaskItem = lipgloss.NewStyle().
+			Foreground(clrText)
+
+	TaskItemFocused = lipgloss.NewStyle().
+			Foreground(clrOrange)
+
+	StatusBar = lipgloss.NewStyle().
+			Foreground(clrText).
+			Background(clrSurface)
+
+	EpicPanel = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrPurple).
+			Background(clrSurface).
+			Padding(0, 1)
+
+	Card = lipgloss.NewStyle().
+		BorderStyle(lipgloss.RoundedBorder()).
+		BorderForeground(clrBorder).
+		Background(clrSurface).
+		Padding(0, 1)
+
+	CardFocused = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrOrange).
+			Background(clrSurface).
+			Padding(0, 1)
+
+	CardMeta = lipgloss.NewStyle().Foreground(clrDim)
+
+	GlyphBuild = lipgloss.NewStyle().Foreground(clrOrange)
+	GlyphTest  = lipgloss.NewStyle().Foreground(clrGreen)
+	GlyphAudit = lipgloss.NewStyle().Foreground(clrPurple)
+
+	DetailOverlay = lipgloss.NewStyle().
+			BorderStyle(lipgloss.RoundedBorder()).
+			BorderForeground(clrOrange).
+			Padding(0, 1)
+
+	// Footer phase styles
+	FooterPhasePlan = lipgloss.NewStyle().
+			Foreground(clrPurple).
+			Bold(true)
+
+	FooterPhaseBuild = lipgloss.NewStyle().
+				Foreground(clrOrange).
+				Bold(true)
+
+	FooterPhaseAudit = lipgloss.NewStyle().
+				Foreground(clrGreen).
+				Bold(true)
+
+	FooterDivider = lipgloss.NewStyle().
+			Foreground(clrBorder)
+
+	FooterHints = lipgloss.NewStyle().
+			Foreground(clrDim)
+
+	// Tag styles for semantic encoding
+	TagDone = lipgloss.NewStyle().Foreground(clrGreen)
+	TagAI   = lipgloss.NewStyle().Foreground(clrPurple)
+)

package/main.go

@@ -0,0 +1,11 @@
+package main
+
+import (
+	"github.com/opencode/savepoint/internal/board"
+)
+
+func main() {
+	if err := board.Run(); err != nil {
+		panic(err)
+	}
+}

package/package.json

@@ -0,0 +1,25 @@
+{
+  "name": "savepoint",
+  "version": "1.0.0",
+  "description": "It’s a simple, file-based state machine and cinematic Terminal UI (TUI) designed to force you—and your agent (Claude, Cursor, Aider, Gemini)—to slow down, write down what you're actually building, and check your work before moving on.",
+  "keywords": [
+    "board",
+    "kanban",
+    "planning"
+  ],
+  "homepage": "https://github.com/anipatke/savepoint#readme",
+  "bugs": {
+    "url": "https://github.com/anipatke/savepoint/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/anipatke/savepoint.git"
+  },
+  "license": "MIT",
+  "author": "anipatke",
+  "type": "Go",
+  "main": "main.go",
+  "scripts": {
+    "test": "savepoint init"
+  }
+}

package/scripts/vitest-preload.cjs

@@ -0,0 +1,95 @@
+const childProcess = require("node:child_process");
+const esbuild = require("esbuild");
+
+const originalExec = childProcess.exec;
+const originalExecFile = childProcess.execFile;
+
+function shouldStub(command) {
+  return (
+    typeof command === "string" && command.trim().toLowerCase() === "net use"
+  );
+}
+
+function fakeChildProcess() {
+  return {
+    pid: 0,
+    kill() {
+      return true;
+    },
+    stdin: null,
+    stdout: null,
+    stderr: null,
+    on() {
+      return this;
+    },
+    once() {
+      return this;
+    },
+    addListener() {
+      return this;
+    },
+    removeListener() {
+      return this;
+    },
+  };
+}
+
+// Vitest probes `net use` on Windows to detect network drive mappings, which fails in this scaffold.
+childProcess.exec = function exec(command, options, callback) {
+  if (shouldStub(command)) {
+    const done = typeof options === "function" ? options : callback;
+    if (typeof done === "function") {
+      setImmediate(() => done(null, "", ""));
+    }
+    return fakeChildProcess();
+  }
+
+  return originalExec.call(this, command, options, callback);
+};
+
+childProcess.execFile = function execFile(file, args, options, callback) {
+  if (shouldStub(file)) {
+    const done =
+      typeof args === "function"
+        ? args
+        : typeof options === "function"
+          ? options
+          : callback;
+    if (typeof done === "function") {
+      setImmediate(() => done(null, "", ""));
+    }
+    return fakeChildProcess();
+  }
+
+  return originalExecFile.call(this, file, args, options, callback);
+};
+
+function identityTransform(input) {
+  const code =
+    typeof input === "string" ? input : (input?.toString("utf8") ?? "");
+  return Promise.resolve({
+    code,
+    map: "",
+    warnings: [],
+    errors: [],
+    mangleCache: {},
+    legalComments: "none",
+  });
+}
+
+function identityTransformSync(input) {
+  const code =
+    typeof input === "string" ? input : (input?.toString("utf8") ?? "");
+  return {
+    code,
+    map: "",
+    warnings: [],
+    errors: [],
+    mangleCache: {},
+    legalComments: "none",
+  };
+}
+
+// Vitest reaches into esbuild on Windows before the real transform path is ready.
+esbuild.transform = identityTransform;
+esbuild.transformSync = identityTransformSync;

package/templates/project/.savepoint/Design.md

@@ -0,0 +1,47 @@
+---
+type: project-design
+status: active
+last_audited: never
+---
+
+# {{PROJECT_NAME}} — System Architecture
+
+> Project-level architecture. Audit-kept fresh: every epic's audit step merges its delta into this document.
+>
+> **Visual identity** lives separately in `.savepoint/visual-identity.md` and is loaded only for TUI/theme/visual tasks.
+
+## 1. Architecture model
+
+<!-- High-level architecture pattern. -->
+
+## 2. Directory layout
+
+<!-- Expected file structure. -->
+
+## 3. Hierarchy semantics
+
+<!-- Definitions of release, epic, task, sub-task. -->
+
+## 4. Status model & gates
+
+<!-- How work moves through states. -->
+
+## 5. Dependencies
+
+<!-- How tasks depend on each other. -->
+
+## 6. CLI surface
+
+<!-- Commands and flags if applicable. -->
+
+## 7. Audit pipeline
+
+<!-- Steps the audit follows. -->
+
+## 8. Testing strategy
+
+<!-- How the project is tested. -->
+
+## 9. Release versioning
+
+<!-- Version scheme. -->

package/templates/project/.savepoint/PRD.md

@@ -0,0 +1,34 @@
+---
+type: project-prd
+status: active
+---
+
+# {{PROJECT_NAME}} — Product Vision
+
+## What it is
+
+<!-- Describe what you are building in one paragraph. Be specific about the core mechanic (e.g., "A CLI tool that uses AI to write unit tests" instead of "An AI coding assistant"). -->
+
+## Why
+
+<!-- What specific problem does this solve? Why does it need to exist now? (e.g., "Developers skip writing tests because it's tedious; this automates the drudgery so coverage stays high without the manual effort.") -->
+
+## Target user
+
+<!-- Who is this for? Be specific. (e.g., "Vibe coders," "Junior frontend developers," "Indie hackers building SaaS MVPs"). If it's for everyone, it's for no one. -->
+
+## Headline differentiator
+
+<!-- What makes this project unique? Why would someone use this over an existing alternative? (e.g., "It integrates directly into the savepoint audit loop, whereas others require a separate PR step.") -->
+
+## Success metrics
+
+<!-- How do you know it's working for V1? (e.g., "Can generate a passing test suite for a 10-file React app in under 60 seconds with zero manual edits.") -->
+
+## Constraints
+
+<!-- Hard limits. What tech stack MUST be used? Are there API cost limits, token limits, or specific libraries you refuse to use? -->
+
+## Out of scope (forever or for now)
+
+<!-- What are you explicitly NOT building for V1? (e.g., "No database. No multi-user login. No web UI.") This is crucial for keeping the AI focused. -->

package/templates/project/.savepoint/config.yml

@@ -0,0 +1,27 @@
+# Savepoint config — single source of truth for project preferences.
+
+verify_strict: false # vibe-coder soft mode; tasks reach done on assertion. Set true for TDD-strict.
+
+quality_gates:
+  lint: null
+  typecheck: null
+  test: null
+  block_on_failure: true
+
+audit:
+  divergence_threshold: 0.5 # warn if a proposal changes >50% of a live file
+
+theme:
+  bg: "#121212"
+  surface: "#0D0D0D"
+  surface_2: "#0F0F0F"
+  border: "#1A1A1A"
+  text: "#F0E6DA"
+  accents:
+    backlog: "#B1A1DF"
+    planned: "#B1A1DF"
+    in_progress: "#FC6323"
+    review: "#FC6323"
+    done: "#A4C639"
+    blocked: "#FF4444"
+  borders: "subtle"

package/templates/project/.savepoint/router.md

@@ -0,0 +1,152 @@
+# Agent State Machine
+
+This file routes the agent based on the project's current state. Read this whenever you start a session.
+
+## Read order on every session
+
+1. This file (you are here)
+2. The current state below to know what to do next
+3. The active epic Design
+4. The active task file, when a task is selected
+
+Read `.savepoint/PRD.md` only for project vision changes. Read `.savepoint/Design.md` only for architecture changes or audit closeout. Read `.savepoint/releases/v{{RELEASE_NUMBER}}/PRD.md` only for release planning or epic-order questions.
+
+**Conditional read (token discipline):** if your active task touches **Ink/TUI implementation**, also read `agent-skills/ink-tui-design/SKILL.md` after Design.md as the execution guide. If it touches **TUI rendering, theme, or visual design**, also read `.savepoint/visual-identity.md` as the visual guardrails. Otherwise skip the extra files — they are tokens you do not need.
+
+## Current state
+
+```yaml
+state: pre-implementation
+release: v{{RELEASE_NUMBER}}
+epic: none
+task: none
+next_action: "The project has its PRD and Design locked but no epics defined yet. Help the user define the epics list and confirm priority."
+```
+
+## Manual audit override
+
+If the user explicitly asks you to audit an epic, perform the audit for that epic even if the router has not reached `state: audit-pending` yet.
+
+Persist the audit artifacts before replying:
+
+- Ensure `.savepoint/audit/{E##-epic}/snapshot.md` exists. Create a manual snapshot once if needed.
+- Write the proposal bundle to `.savepoint/audit/{E##-epic}/proposals.md`.
+- Do not stop at chat-only findings. The filesystem artifact is part of the task output.
+
+## State → next action
+
+<!-- AGENT: Read the state above. Find the matching block below. Follow it. -->
+
+### `state: pre-implementation`
+
+The project has its PRD and Design locked but no epics defined yet.
+
+**Next action:**
+
+1. Read `.savepoint/releases/v{{RELEASE_NUMBER}}/PRD.md` — the v{{RELEASE_NUMBER}} release scope (epic list lives there).
+2. Help the user define the epics list and confirm priority.
+3. For each epic in order, create the directory `.savepoint/releases/v{{RELEASE_NUMBER}}/epics/E##-{epic-name}/` with a `Design.md` stub.
+4. When epic E01 (scaffolding) is created, transition to `state: epic-design` for that epic.
+
+**Do not** start writing code. We are still in planning.
+
+### `state: epic-design`
+
+An epic exists but its `Design.md` is empty or a stub.
+
+**Next action:** Walk the user through filling out the epic's `Design.md`:
+
+- What is this epic adding to the system?
+- What components / files does it touch?
+- What's the architectural delta vs the current state?
+
+When complete, transition to `state: epic-task-breakdown` for this epic.
+
+### `state: epic-task-breakdown`
+
+Epic Design exists but tasks are missing or not fully planned.
+
+**Next action:**
+
+1. Re-read the epic Design.
+2. Create or update the full epic task list — each task **independently buildable**, **objective-led**, with declared `depends_on`.
+3. Each task file lives at `.savepoint/releases/v{{RELEASE_NUMBER}}/epics/{E##-epic}/tasks/TNNN-slug.md` with frontmatter:
+   ```yaml
+   ---
+   id: {E##-epic}/TNNN-slug
+   status: planned
+   objective: "<one sentence>"
+   depends_on: []
+   ---
+   ```
+4. In the same pass, write each task's `## Acceptance Criteria` (observable outcomes that define "done") and `## Implementation Plan` (the build checklist that satisfies them) as inline `- [ ]` checkboxes, plus a `## Context Log` section with `Files read`, `Estimated input tokens`, and `Notes` fields.
+5. When every task is planned, transition to `state: task-building` for the first unblocked task.
+
+### `state: task-planning`
+
+Reserved for repair or late-added tasks. Normal epic planning happens during `state: epic-task-breakdown`.
+
+**Next action:** Read the task's `objective`. Write `## Acceptance Criteria` (observable outcomes) before `## Implementation Plan` (build checklist). Use inline `- [ ]` checkboxes under the plan, add a `## Context Log` section, set `status: planned`, and stop.
+
+### `state: task-building`
+
+Task is `in_progress`. All `depends_on` are `done`.
+
+**Next action:** Execute the plan. Tick checkboxes as you complete them. The implementation checklist exists to satisfy the task's acceptance criteria; every checked box should map to an observable outcome in `## Acceptance Criteria`. Edit code per the **Code Style** rules in `AGENTS.md`. Before setting `status: done`, update the task's `## Context Log`. When all checkboxes tick, run the full quality-gate suite, set `status: done`, update the router, and **stop for user review**.
+
+**Do not start the next task without user acknowledgment.**
+
+### `state: audit-pending`
+
+The last task in an epic is `done`. Audit must run before the next epic starts.
+
+**Context gate:** If you just built this epic in the current session, you **must not** audit it. Close this session. The user should start a new session for the audit.
+
+**Next action (fresh session only):** Confirm `.savepoint/audit/{E##-epic}/snapshot.md` exists. If it is missing while the audit CLI is still unavailable, create one manual snapshot from the known epic scope once; do not search broadly for replacement inputs. Then read the snapshot, read the epic's `Design.md`, and read only the files listed as changed. Write one patch-shaped proposal bundle to `.savepoint/audit/{E##-epic}/proposals.md`:
+
+- `Design.md` section — merge only the epic delta into project architecture.
+- `AGENTS.md` section — refresh Codebase Map entries from changed-module metadata; preserve existing rows.
+- `epic-Design.md` section — add "Implemented as:" notes and deltas from the original plan.
+- `Quality Review` section — semantic-review findings against the 10 Code Style rules.
+
+Prefer delta-only edits (`Insert After`, `Replace`, `Delete`) anchored to exact text. Do not quote and replace entire large sections unless the whole section genuinely changed.
+
+Proposal format:
+
+```md
+## Target File
+
+`path/to/file.md`
+
+## Replace
+
+<exact old heading, marker, or section>
+
+## With
+
+<new content>
+```
+
+Quality review section format:
+
+```md
+## Must Fix Before Close
+
+## Must Fix Before Next Epic
+
+## Carry Forward
+
+## Already Fixed
+```
+
+After proposals are approved, apply approved proposals to live files, mark the epic `Design.md` as `status: audited`, update project `Design.md` `last_audited`, refresh `AGENTS.md` Codebase Map, and advance this router to the next epic state.
+
+Stop. The user reviews proposals in the TUI before commit actions.
+
+## Capability check
+
+If you are not Claude Opus / Gemini 2.5 Pro / GPT-5.5 / equivalent, surface a warning to the user:
+
+> _"Heads up — I'm running on a lighter model. Savepoint's planning steps work best with top-tier models because the embedded prompts are detailed. I'll do my best, but consider switching the model for PRD/Design/Task-breakdown steps."_
+
+Then proceed.

package/templates/project/.savepoint/visual-identity.md

@@ -0,0 +1,122 @@
+---
+type: visual-identity
+status: active
+last_audited: never
+---
+
+# Visual Identity — Atari-Noir
+
+> The brand identity and visual guardrails for {{PROJECT_NAME}}. **Loaded conditionally** — only when working on TUI rendering, theme, or design-system tasks. Non-visual tasks must skip this file to honor the token budget.
+
+## Vibe
+
+A serious digital system that loves old arcade hardware. Dark, cinematic, playful. Crisp, not noisy. Technical, not cold.
+
+**Avoid:** neon cyberpunk chaos, SaaS minimalism, fake terminal gimmicks.
+
+## Palette
+
+| Element       | Hex       | Role                          |
+| ------------- | --------- | ----------------------------- |
+| Background    | `#121212` | Main screen background        |
+| Surface       | `#0D0D0D` | Cards and panels              |
+| Surface 2     | `#0F0F0F` | Secondary panels / title bars |
+| Border        | `#1A1A1A` | Quiet structural edges        |
+| Border Subtle | `#222222` | Slightly stronger separators  |
+| Primary Text  | `#F0E6DA` | Warm off-white terminal text  |
+| Atari Orange  | `#FC6323` | Primary CTA, active highlight |
+| NPP Green     | `#A4C639` | Success, live systems         |
+| Vibe Purple   | `#B1A1DF` | AI, reflection                |
+
+**Color rules:**
+
+- **Intentional accents.** One accent color per major section/type. Use for labels, hover, glows, active text — never giant background fills.
+- **Dark backgrounds.** Keep them dark so accents pop.
+- **Visual encoding.** Color semantically encodes categories or states; reinforce with minimal text.
+
+## Typography
+
+- **System heading font:** `Chakra Petch` (web only — terminal cannot control fonts)
+- **System body/UI font:** `Space Mono` (web only — terminal cannot control fonts)
+- **Accent retro fonts:** `Silkscreen` or `Press Start 2P`, used rarely for score counters or deliberately extreme moments
+
+**Rules:**
+
+- Headings uppercase, with deliberate letter-spacing where the medium allows.
+- Body readable and restrained; abandon monospace for long text if readability suffers.
+- Render magnitude/comparison numbers as proportional visuals (bars, circles), not raw values.
+
+## Spacing rhythm
+
+- Sections breathe. Default spacing feels generous.
+- Cards have enough internal padding to feel like panels, not chips.
+- Whitespace creates hierarchy before borders or color do.
+
+## Signature UI patterns
+
+- **Scanlines** — low-opacity CRT atmosphere; never obscure readability.
+- **Glows** — radiate from perimeter ("lit from within"). Transparent section accent colors; no neon spam.
+- **Panels** — flat, dark, structured with quiet borders. Depth from contrast/glow, not heavy shadows.
+- **Search** — simple, single-line; integrated with section accent color.
+- **MDX prose** — integrated using standard typography, palette, border logic.
+
+## Interaction principles ("The Playable Dashboard")
+
+**Content is the interface.** Avoid traditional UI patterns (dropdowns, accordions) if content can express the information directly.
+
+- **Show, don't explain.** Visuals (scaled circles, markers) before text.
+- **Motion** — authored, not generic. Ease like a system booting up. No bouncy toy motion.
+- **Hover & focus** — internal light (underglow/surface tint), not thick outlines or loud transforms.
+- **Expansion** — breathe open, don't snap. Inline reveals, shared-element transitions.
+
+## Replication brief
+
+If recreating this look-and-feel, preserve:
+
+- dark charcoal background with warm off-white text
+- three-color accent system (one per major section)
+- `Chakra Petch` for headings, `Space Mono` for body/UI (where typography can be controlled)
+- uppercase, tracked headings
+- quiet borders, dark surfaces, selective glow
+- one strong interactive hero element
+- copy that sounds human, competent, intentionally non-corporate
+- **Young Explorer Baseline:** all content and visuals understandable by a 7-year-old. Intuitive visual metaphors, no unexplained jargon, discoverable through play.
+
+**Family resemblance, not exact duplication.** Preserve the underlying feel, hierarchy, restraint.
+
+## Flex & constraints
+
+- **Layout & components:** can adapt to content needs, provided palette discipline and tonal restraint remain.
+- **Fonts:** supporting fonts can vary if heading/body contrast remains.
+- **Hero:** interaction can vary, but requires one strong, ownable interactive element.
+- **Visual-first:** show relationships visually before explaining them in text (gradient bar > numbers). Text reinforces; visuals carry comprehension.
+- **Cognitive accessibility:** anchor complex concepts to physical/visual analogies a 7-year-old can grasp.
+
+## What survives in the terminal
+
+| Web rule                            | Terminal feasibility | Adaptation                                                       |
+| ----------------------------------- | -------------------- | ---------------------------------------------------------------- |
+| Dark bg + warm off-white text       | ✓                    | 24-bit color with 256/16-color fallbacks                         |
+| 3-color accent system               | ✓                    | per status, per epic, per section                                |
+| `Chakra Petch` / `Space Mono` fonts | ✗                    | terminal owns the font; README discloses                         |
+| Uppercase tracked headings          | ⚠                    | uppercase yes; letter-spacing no (fixed-width cells)             |
+| Scanlines                           | ✗                    | flicker/ugly in text — skip                                      |
+| Glows / underglow                   | ⚠                    | substitute with subtle bg tint on focused row + accent border    |
+| Quiet borders, dark surfaces        | ✓                    | box-drawing chars (`─ │ ┌ ┐`) in border-subtle gray              |
+| Inline reveal cards                 | ✓                    | Ink state-driven expand/collapse                                 |
+| Visual encoding before text         | ✓                    | colored glyphs (`▣ ◇ ◆ ✓`) with text reinforcement               |
+| "System booting up" motion          | ⚠                    | 200ms init sequence on launch acceptable; running animation skip |
+
+## Terminal UI guardrails
+
+- Keep UI state explicit and local to the smallest useful surface.
+- Use project data files as the source of truth; do not invent hidden UI state.
+- Keep layout compact and readable on narrow terminals first.
+- Treat accidental line wrapping as a bug.
+- Make selection, focus, and status changes obvious without relying on color alone.
+- Make every keyboard action predictable and idempotent.
+- Test branching input handling, navigation, state transitions, render output, and non-TTY fallbacks.
+
+## When `savepoint init` ships
+
+This file is the canonical default that `savepoint init` writes into a user's `.savepoint/visual-identity.md`. Users replace it with their own design system. The file's existence (not its contents) is what `savepoint` cares about.