savepoint 1.0.4 → 1.0.6

package/.savepoint/releases/v1.1/epics/_archived/T004-ai-reconcile.md

@@ -1,29 +0,0 @@
----
-id: E06-audit-command/T004-ai-reconcile
-status: planned
-objective: "Generate AI prompt for semantic review, parse findings"
-depends_on: ["E06-audit-command/T003-snapshot"]
----
-
-# T004: AI Reconcile (Semantic Review)
-
-## Acceptance Criteria
-
-- Generates a prompt file for human to give to their AI
-- Prompt includes: snapshot, epic E##-Detail.md, changed files list, AGENTS.md Code Style rules
-- Prompt instructs AI to check against 10 Code Style rules
-- After human runs AI, parses findings for "Must Fix Before Close" section
-- Fails audit if "Must Fix Before Close" has any items
-
-## Implementation Plan
-
-- [ ] Add `internal/audit/reconcile.go`
-- [ ] Implement `GeneratePrompt(epic, release) (string, error)`
-- [ ] Embed 10 Code Style rules in prompt template
-- [ ] Include snapshot.md content in prompt
-- [ ] Include epic E##-Detail.md in prompt
-- [ ] Include changed files list in prompt
-- [ ] Implement `ParseFindings(output) (hasIssues bool, err)`
-- [ ] Check for "Must Fix Before Close" header and non-empty content
-- [ ] Test prompt generation and finding parsing
-- [ ] Run `make build && make test`

package/.savepoint/releases/v1.1/epics/_archived/T006-tui-review.md

@@ -1,31 +0,0 @@
----
-id: E06-audit-command/T006-tui-review
-status: planned
-objective: "Implement TUI review mode for approving/rejecting proposals"
-depends_on: ["E06-audit-command/T005-proposals"]
----
-
-# T006: TUI Review Mode
-
-## Acceptance Criteria
-
-- Shows each proposal as a side-by-side diff (old vs new)
-- User can Approve, Reject, or Edit each proposal
-- Edit opens inline editor to modify the "With" section
-- High-divergence warning if proposal changes >50% of file
-- Shows progress: X of Y proposals reviewed
-- Keyboard: arrow nav, Enter approve, Backspace reject, e edit, q quit
-
-## Implementation Plan
-
-- [ ] Add `internal/audit/review.go` with Bubble Tea model
-- [ ] Create `ReviewModel` with proposals, current index, decisions
-- [ ] Implement `RenderProposal` showing old/new side-by-side
-- [ ] Add keyboard handlers: Up/Down (nav), Enter (approve), Backspace (reject), e (edit)
-- [ ] Implement edit mode: text area for "With" content
-- [ ] Add high-divergence check (config threshold from config.yml)
-- [ ] Show progress bar: "Proposal 1 of 5"
-- [ ] Track decisions: approved/rejected/edited map
-- [ ] Return decisions to caller for apply step
-- [ ] Test review flow manually
-- [ ] Run `make build && make test`

package/.savepoint/releases/v1.1/epics/_archived/T008-skip-handling.md

@@ -1,34 +0,0 @@
----
-id: E06-audit-command/T008-skip-handling
-status: planned
-objective: "Implement audit skip with logging"
-depends_on: ["E06-audit-command/T001-cli-entrypoint"]
----
-
-# T008: Skip Handling
-
-## Acceptance Criteria
-
-- `--skip --reason "..."` flags are required together
-- Missing reason shows error
-- Skipped audit logged to `.savepoint/audit-log.md`
-- Log entry includes: timestamp, epic, release, reason, skipped-by
-- Skipped epic still advances router (no changes to docs)
-
-## Implementation Plan
-
-- [ ] Add `internal/audit/log.go`
-- [ ] Implement `LogSkip(epic, release, reason) error`
-- [ ] Parse existing audit-log.md or create new
-- [ ] Append new entry in format:
-    ```markdown
-    ## {timestamp}
-
-    - **Epic:** {epic}
-    - **Release:** {release}
-    - **Reason:** {user reason}
-    - **Status:** ⚠ skipped
-    ```
-- [ ] Update router to advance past skipped epic
-- [ ] Test skip flow with valid/invalid args
-- [ ] Run `make build && make test`

package/.savepoint/releases/v1.1/v1.1-PRD.md

@@ -1,139 +0,0 @@
----
-version: 1.1
-name: "Board Polish & Navigation"
-status: in_progress
----
-
-# Release v1.1 — Board Polish & Navigation
-
-## Overview
-
-v1.1 is the "love what you look at" release. It takes the functional board from v1 and makes it polished, reliable, and pleasant to navigate. The four epics cover layout robustness, multi-platform tooling, visual refinement, and a new epic navigation paradigm.
-
-**v1 delivered:** a working Kanban board with phase transitions.
-**v1.1 delivers:** a board that doesn't flicker on resize, builds everywhere, looks intentional, and treats epics as first-class navigable objects.
-
-## What ships in v1.1
-
-1. **TUI Optimisation (E01)** ✅ *Audited and complete*
-   - Next Activity indicator in header
-   - Naming conventions reconciled (Design.md → E##-Detail.md, PRD.md → v1-PRD.md)
-   - Virtual viewport scrolling for columns and detail overlay
-   - Column focus border stability — no content shift when switching columns
-   - All 7 tasks done
-
-2. **Cross-Platform Compatibility (E02)** — *Not started*
-   - `make build`, `test`, `clean` work on Windows, Linux, macOS
-   - Linux amd64 + arm64 and macOS amd64 + arm64 build targets
-   - Smoke tests and versioned release artifacts
-   - 4 tasks planned
-
-3. **UI Visual Refinement (E03)** — *Not started*
-   - Right-border clipping fixed on terminal resize
-   - Next Activity as a dedicated line below header with phase-aligned styling
-   - Checkbox rendering at sentence boundaries
-   - Width arithmetic audit — content fills available space exactly
-   - 4 tasks planned
-
-4. **Epic Navigation (E04)** — *Not started*
-   - Epic sidebar becomes a focusable, navigable component
-   - ↑/↓ to navigate epics, ←/→ to enter/exit sidebar
-   - Enter opens an "Epic Detail" overlay showing E##-Detail.md content
-   - Existing `E` key dropdown retained
-   - 2 tasks planned
-
-5. **Tasking Permissions & Router Updates (E05)** ✅ *Audited and complete*
-   - Agents can only set `status: in_progress`; user alone sets `done` or retreats
-   - New TUI `p` priority hotkey explicitly updates router to the focused non-done task
-   - Router task priority decoupled from navigation — browse without side effects
-   - Priority writes keep router in `task-building`; audit handoff remains explicit
-   - All 6 tasks done
-
-6. **Audit Command (E06)** — *Planned*
-   - `savepoint audit <epic-id|release>` runs full pipeline
-   - Quality gates block on failure
-   - AI semantic review checks 10 Code Style rules — blocks if "Must Fix Before Close" has items
-   - TUI review mode for approving/rejecting proposals
-   - Updates Design.md last_audited, marks epic status: audited
-   - 9 tasks planned
-
-7. **Init Command (E07)** — *Planned*
-   - `savepoint init [dir] [--force] [--install]` scaffolds .savepoint/
-   - Target validation (empty/compatible/already-initialized)
-   - Template-based scaffold with project name interpolation
-   - Magic prompt output to stdout + clipboard
-   - Best-effort clipboard (doesn't fail on error)
-   - 7 tasks planned
-
-8. **Board Command (E08)** — *Planned*
-   - `savepoint board [--release <release>] [--epic <epic>]` launches TUI
-   - `savepoint` (no args) defaults to board
-   - Bubble Tea TUI with 3-column Kanban
-   - Detail pane for selected task
-   - Keyboard navigation (arrows, vim-style j/k/h/l)
-   - Status transitions with gate enforcement
-   - Non-TTY plain table fallback
-   - 8 tasks planned
-
-9. **Doctor Command (E09)** — *Planned*
-   - `savepoint doctor [--epic <epic>]` runs diagnostics
-   - Config, router, structure, YAML validation
-   - Dependency checks (missing deps, cycles, duplicates)
-   - Audit state and orphan detection
-   - Ad-hoc quality gate runner
-   - Human-readable diagnostic output with repair suggestions
-   - Exit codes: 0=clean, 1=problems, 2=error
-   - 6 tasks planned
-
-10. **Task File Validation & Auto-Fix (E12)** — *In Progress*
-     - Default `phase: build` when `status=in_progress` but phase missing
-     - Default `status: planned` when both status and column missing
-     - Better error hints with suggested fixes
-     - Validate on write with helpful messages
-
-11. **Codebase Audit Remediation (E13)** — *In Progress*
-    - Fix cycle detection bug producing inaccurate error paths
-    - Remove dead code, stdlib reimplementations, hardcoded state maps
-    - Centralize duplicated logic (normalization, frontmatter extraction, shared utilities)
-    - Fix AtomicWrite cross-device fallback and config accent defaults
-    - Add quality gate timeout
-    - Remove committed binaries, add gitignore and linter config
-    - Decompose `update.go` monolith into focused handlers
-    - Extract synchronous I/O from `Update()` into `tea.Cmd` async pattern
-    - Add test coverage for untested packages
-    - 7 tasks planned
-
-## Epic breakdown
-
-| # | Epic | Status | Tasks |
-|---|------|--------|-------|
-| 01 | TUI Optimisation | Audited | 7/7 done |
-| 02 | Cross-Platform Compatibility | Audited | 4/4 done |
-| 03 | UI Visual Refinement | Planned | 0/4 done |
-| 04 | Epic Navigation | Audited | 2/2 done |
-| 05 | Tasking Permissions & Router Updates | Audited | 6/6 done |
-| 06 | Audit Command | Planned | 0/9 done |
-| 07 | Init Command | Planned | 0/7 done |
-| 08 | Board Command | Planned | 0/8 done |
-| 09 | Doctor Command | Planned | 0/6 done |
-| 10 | Task File Validation & Auto-Fix | In Progress | 5/5 done |
-| 13 | Codebase Audit Remediation | In Progress | 0/7 done |
-
-## Success criteria
-
-- `make build` and `make test` pass on Windows, Linux, and macOS
-- Terminal resize at any width ≥ 40 produces no visual corruption
-- Content fills the available terminal width exactly at every breakpoint
-- Epic sidebar is navigable with ↑/↓, and Enter shows a detail overlay
-- All existing v1 functionality is preserved unchanged
-- `go build ./...` and `go test ./...` pass
-
-## Known issues
-
-- E03 has `Design.md` instead of the expected `E03-Detail.md` — rename to match convention (tracked in E01/T002 scope, may need a follow-up task)
-
-## Risks
-
-- **Build tooling scope creep.** E02 is pure Makefile work, but smoke-testing on non-Windows requires either CI or manual verification on actual Linux/macOS.
-- **Naming convention holdout.** E03's `Design.md` may cause discovery or rendering issues if the board ever reads `E##-Detail.md` by pattern. Low priority — handled as a rename task if needed.
-- **Epic panel is ≥120 only.** E04's features require a wide terminal — users on narrow terminals still use the `E` key dropdown.

package/.savepoint/router.md

@@ -1,57 +0,0 @@
-# Agent State Machine
-
-## Read order
-
-1. This file (router.md)
-2. Current state → next action
-3. Active epic E##-Detail.md
-4. Active task file
-
-Read `.savepoint/PRD.md` only for vision changes. Read `.savepoint/Design.md` only for architecture/audit.
-
-## Current state
-
-```yaml
-state: epic-design
-release: v1.1
-epic: ""
-task: ""
-next_action: Plan next epic.
-```
-
-## State → action
-
-### pre-implementation
-
-PRD + Design locked, no epics yet.
-
-**Next:** 1) Read release PRD for epic list, 2) Define + confirm epic order, 3) Create epic stubs. Transition to `epic-design` for E01.
-
-### epic-design
-
-Epic E##-Detail.md is empty/stub.
-
-**Next:** Define what this epic adds, files it touches, and architectural delta. Then transition to `epic-task-breakdown`.
-
-### epic-task-breakdown
-
-Epic exists, tasks missing.
-
-**Next:** 1) Re-read epic, 2) Create task files at `tasks/TNNN-slug.md` with `status: planned`, `objective`, `depends_on`, 3) Add `## Implementation Plan` checkboxes per task. When all planned → first unblocked task.
-
-### task-building
-
-Task `in_progress`, depends satisfied.
-
-**Next:** When starting work, set task `status: in_progress` and press `p` in TUI to mark the focused task as router priority. Execute plan, tick checkboxes, run quality gates, update router to next task or `audit-pending`. Stop.
-
-### audit-pending
-
-Epic complete, needs audit before next epic.
-
-**Next:** Fresh audit agent reads epic E##-Detail.md, task files, drift notes, Design.md, AGENTS.md, and scoped changed files. Write one audit file to `.savepoint/releases/{release}/epics/{E##-epic}/E##-Audit.md`:
-- `## Main Findings` user-facing narrative only
-- `## Code Style Review` checklist against AGENTS.md rules
-- `## Proposed Changes` admin/apply blocks using `### Target File`, `### Replace`, `### With`
-
-After user approves: apply proposals, mark epic `status: audited`, update Design.md `last_audited`, advance router.

package/.savepoint/visual-identity.md

@@ -1,125 +0,0 @@
----
-type: visual-identity
-status: active
-last_audited: never
----
-
-# Visual Identity — Atari-Noir
-
-> The brand identity and visual guardrails for savepoint. **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.
-
-For Ink/TUI implementation mechanics, use `agent-skills/ink-tui-design/SKILL.md`. This file only owns visual and product-design constraints.
-
-## 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    | `#000000` | Uniform terminal background   |
-| Surface       | `#000000` | Cards and panels; same black as background |
-| Surface 2     | `#000000` | Secondary panels / title bars; same black as background |
-| 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.
-- **Uniform terminal black.** In the TUI, Background, Surface, and Surface 2 intentionally remain the same black value. Do not reintroduce subtly different panel background fills; hierarchy comes from spacing, dividers, glyphs, and accent borders.
-- **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.

package/AGENTS.md

@@ -1,99 +0,0 @@
-# Agents Guide
-
-## Workflow
-
-1. Read `.savepoint/router.md` — state + next action
-2. Activate skill per table below
-3. Read: router → epic → task → source files
-
-## Skill Activation
-
-| State | Skill |
-|-------|-------|
-| pre-implementation | savepoint-draft-prd |
-| epic-design | savepoint-system-design |
-| epic-task-breakdown | savepoint-create-task |
-| task-building | savepoint-build-task |
-| audit-pending | savepoint-audit |
-
-Use the `skill` tool when the listed skill is available. If the agent says the skill is not found, read `agent-skills/{skill}/SKILL.md` directly and follow it as the active skill.
-
-Read `.savepoint/PRD.md` only for vision changes, `.savepoint/Design.md` only for architecture/audit.
-
-## Task Status
-
-- `status`: only `planned`, `in_progress`, or `done`
-- `stage` (build/test/audit): **required** when `status: in_progress` — omitting it is a parse error
-- Never: todo, doing, blocked, review, audit
-- Agents may set a task to `status: in_progress` when starting implementation.
-- Only the user may set a task to `status: done` or retreat a task to an earlier status.
-
-## Implementation
-
-1. Read task's `## Context Files` using `Read` tool — one call per file, no explore, no glob
-2. Read task's `## Acceptance Criteria` + `## Implementation Plan`
-3. When starting implementation, set task frontmatter to `status: in_progress` + `stage: build` (both required together)
-4. After setting `in_progress`, press `p` in the TUI to mark the focused task as router priority
-5. Execute in order, tick checkboxes
-6. Verify every AC has passing test/outcome
-7. Run quality gates (build + test)
-8. Update router.md: next task or `audit-pending`
-9. **Stop. Prompt user before continuing.**
-
-## Drift Check
-
-- New files/modules not in Codebase Map?
-- Architecture changed from Design.md?
-
-If yes → append `## Drift Notes` to task file.
-
-## Audit Handoff
-
-The agent that builds an epic **must not audit it**. Start a fresh session.
-
-## Audit File Structure
-
-- Audit is agent-led via `savepoint-audit`, not a `savepoint audit` CLI pipeline.
-- Write exactly one `.savepoint/releases/{release}/epics/{E##-slug}/E##-Audit.md`.
-- The TUI Audit tab renders `## Main Findings` and `## Code Style Review` only.
-- Keep file-specific `### Target File` / `### Replace` / `### With` blocks under `## Proposed Changes` so admin apply details do not appear in the Epic Detail panel.
-- During audit apply/close, update the same `E##-Audit.md` visible sections so `## Main Findings` and `## Code Style Review` describe the applied outcome, not stale pre-apply blockers.
-
-## Code Style
-
-- **One job per file** — split files when responsibilities mix.
-- **One job per function** — small, named, testable units.
-- **Test branches** — cover meaningful conditionals and edge cases.
-- **Types document intent** — prefer explicit types over comments.
-- **Build only what is needed** — no speculative abstractions.
-- **Handle errors at boundaries** — validate inputs, APIs, IO, and external data.
-- **One source of truth** — no duplicated rules, constants, state, or config.
-- **Comments explain why** — not what the code already says.
-- **Content lives in data** — keep copy/config out of logic.
-- **Small diffs** — minimal, reviewable, behaviour-preserving changes.
-
-## Build
-
-```bash
-make build && make test
-```
-
-## Codebase Map
-
-| Module | Purpose |
-|--------|---------|
-| `main.go` | CLI entrypoint, --version |
-| `cmd/` | CLI command arg parsing and dispatch for init, board, and doctor |
-| `internal/init/` | Target validation, scaffold writing from templates |
-| `internal/board/` | TUI board, overlays, epic sidebar, Next Activity line, router priority key, detail checklist rendering, status glyphs, forced color profile, debug logging hooks, async update I/O commands, shared board utilities |
-| `internal/buildtool/` | Makefile helper, cross-compile including Windows targets, archives, distribution checksums |
-| `internal/doctor/` | Read-only project diagnostics, integrity checks, timed quality gate execution, report formatting, typed repair suggestions |
-| `internal/data/` | Task/router models, frontmatter parsing/splitting, lifecycle validation/defaulting, discovery including root-dir traversal, unified task status constants, canonical write helpers |
-| `internal/testutil/` | Shared Go test fixtures and filesystem helpers for internal package tests |
-| `internal/styles/` | Atari-Noir palette, TUI styles |
-| `templates/` | Scaffold markdown, YAML, prompts |
-| `agent-skills/` | Phase-specific skill guides |
-
-## CLI Rules
-
-**Never run `savepoint` commands.** The CLI is for the human. Edit files directly.

package/CLAUDE.md

@@ -1 +0,0 @@
-See `AGENTS.md` at the project root.

package/GEMINI.md

@@ -1 +0,0 @@
-See `AGENTS.md` at the project root.

package/Makefile

@@ -1,31 +0,0 @@
-.PHONY: build test run clean build-linux build-darwin build-all dist smoke-test ci
-
-VERSION ?=
-
-build:
-	go run ./internal/buildtool -version "$(VERSION)" build
-
-test:
-	go test ./...
-
-run:
-	go run main.go
-
-clean:
-	go run ./internal/buildtool -version "$(VERSION)" clean
-
-build-linux:
-	go run ./internal/buildtool -version "$(VERSION)" build-linux
-
-build-darwin:
-	go run ./internal/buildtool -version "$(VERSION)" build-darwin
-
-build-all: build-linux build-darwin
-
-dist:
-	go run ./internal/buildtool -version "$(VERSION)" dist
-
-smoke-test:
-	go run ./internal/buildtool -version "$(VERSION)" smoke-test
-
-ci: test build