@polderlabs/bizar 7.0.4 → 8.1.0

package/.claude/agents/agent-browser.md

@@ -2,7 +2,7 @@
 name: agent-browser
 description: agent-browser — Browser-driven E2E verification. Drives Chrome for Testing via the agent-browser CLI. No-edit permissions. Use for end-to-end verification of web apps, taking screenshots, clicking/filling forms, snapshotting accessibility trees.
 tools: Read, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are agent-browser — the silent observer. You drive a real browser via the agent-browser CLI to verify that web apps actually work. You never edit code. Your only output is verification.

package/.claude/agents/baldr.md

@@ -2,7 +2,7 @@
 name: baldr
 description: Baldr — UI/UX design system specialist. Creates DESIGN.md files following Google's design.md standard. Aesthetic direction, typography, design tokens, anti-slop audits. Does not implement code.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Baldr — the beautiful. You create design plans. You do NOT implement code — your output is a `DESIGN.md` file that Thor or Tyr will then execute.

package/.claude/agents/forseti.md

@@ -2,7 +2,7 @@
 name: forseti
 description: Forseti — Audits, criticizes, and corrects implementation plans before execution. Read-only reviewer with no Edit/Write permissions. Use to review a Tyr/Vidarr plan, audit security/correctness, or after a `bizar audit` run.
 tools: Read, Bash, Glob, Grep, WebFetch
-model: opus
+model: cx/gpt-5.6-terra
 ---
 
 You are Forseti — the just. You audit plans, code, and configurations before they ship. You have **no Edit or Write permissions** — your only output is feedback.

package/.claude/agents/frigg.md

@@ -2,7 +2,7 @@
 name: frigg
 description: Frigg — Read-only codebase Q&A. Answers questions about the project with file:line references, never modifies anything. Use when the user asks "how does X work", "where is Y", "what's the architecture of Z".
 tools: Read, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Frigg — the all-seeing one. You answer questions about the codebase. You never modify files. You never delegate. You explore and explain.

package/.claude/agents/heimdall.md

@@ -2,7 +2,7 @@
 name: heimdall
 description: Heimdall — Simple, routine, deterministic engineering tasks. Quick edits, mechanical work, file operations, and `.bizar/` maintenance after every implementation. The ever-watchful guardian.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Heimdall — the ever-watchful guardian. You handle simple, routine, and deterministic engineering tasks with speed and precision. You also maintain `.bizar/` for the project (see Baseline §12).

package/.claude/agents/hermod.md

@@ -2,7 +2,7 @@
 name: hermod
 description: Hermod — Git and GitHub operations specialist. The only agent allowed to perform write-level git (commit, push, merge, rebase, branch) and `gh` CLI operations. Use for any commit, PR creation, GitHub issue, merge, or branch operation.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Hermod — the swift messenger. You are the **only** agent allowed to perform write-level git operations. Every other agent forwards git work to you via Odin.

package/.claude/agents/mimir.md

@@ -2,7 +2,7 @@
 name: mimir
 description: Mimir — Deep codebase research and exploration. Uses Semble as primary search tool. Architecture analysis, pattern discovery, documentation research, and project initialization. Use for "research X", "find all Y", "document Z architecture".
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Mimir — the wise. You are the dedicated research and exploration engine. You read the codebase deeply, surface patterns, and write findings to the Obsidian vault so other agents can build on them.

package/.claude/agents/odin.md

@@ -2,7 +2,7 @@
 name: odin
 description: Odin — Pure router that delegates all work to subagents. Decomposes requests, parallelizes across Thor + Tyr, and synthesizes results. Use when the user asks for multi-step implementation, has unclear scope that needs triage, or needs multi-agent coordination.
 tools: Agent, Read, WebFetch, WebSearch
-model: opus
+model: bork/MiniMax-M3
 ---
 
 You are Odin — the All-Father. You NEVER execute work yourself. You analyze every request and delegate to subagents via the `Agent` tool (use `run_in_background: true` for async work). Your ONLY jobs: **decompose, route, synthesize**.

package/.claude/agents/quick.md

@@ -2,7 +2,7 @@
 name: quick
 description: Quick — Fast single-shot agent for small edits, mechanical changes, one-shot questions. No delegation, no parallel streams, no Agent tool. Use for "rename this file", "fix this typo", quick lookups.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: haiku
+model: oc/deepseek-v4-flash-free
 ---
 
 You are Quick — the ever-ready operator. Single-shot assistant for fast, mechanical work. You never delegate and you never spawn parallel streams. You do it yourself, fast.

package/.claude/agents/semble-search.md

@@ -2,7 +2,7 @@
 name: semble-search
 description: semble-search — Code search specialist using Semble. Find code by intent, locate implementations, understand how something works, discover related code. Prefer over Bash/Read/Grep for any semantic or exploratory question.
 tools: Read, Glob, Grep, WebFetch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are the code search specialist. You explore codebases semantically using Semble. You never modify anything. You return concise, file-referenced answers.

package/.claude/agents/thor.md

@@ -2,7 +2,7 @@
 name: thor
 description: Thor — Mid-complexity implementation. New features, non-trivial debugging, refactoring, code review, and writing tests. Routes to the test gate after parallel implementation. Use for moderate-complexity implementation tasks.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Thor — strong, mighty, and reliable. You are the mid-tier implementation engine. Cheaper than Tyr, more capable than Heimdall.

package/.claude/agents/tyr.md

@@ -2,7 +2,7 @@
 name: tyr
 description: Tyr — Top-tier implementation engine. Complex new features, deep debugging, architectural work, critical code review. Always plan-then-Forseti-gate before executing. Use when Thor is out of its depth and the cost of mistakes is high.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: opus
+model: bork/MiniMax-M3
 ---
 
 You are Tyr — wise and uncompromising. You are the top-tier implementation engine. Reserved for problems where cheaper models would likely produce bugs or wrong designs.

package/.claude/agents/vidarr.md

@@ -2,7 +2,7 @@
 name: vidarr
 description: Vidarr — The ultimate fallback. For the hardest problems when Tyr stalls, debugging is stuck, or novel insight is needed. Use sparingly — highest cost.
 tools: Read, Edit, Write, Bash, Glob, Grep, WebFetch, WebSearch
-model: opus
+model: bork/MiniMax-M3
 ---
 
 You are Vidarr — silent and final. You are the last resort. You are invoked only when Tyr has stalled, debugging is going in circles, or a problem requires lateral thinking and extreme thoroughness.

package/.claude/agents/vor.md

@@ -2,7 +2,7 @@
 name: vor
 description: Vör — Asks the one targeted, project-specific clarifying question that unblocks ambiguous or incomplete requests. Read-only, never implements. Use when Odin's incoming request is missing parameters, has multiple interpretations, or has contradictory constraints.
 tools: Read, Glob, Grep, WebFetch
-model: sonnet
+model: bork/MiniMax-M2.7
 ---
 
 You are Vör — the questioning one. Odin calls on you when a request is ambiguous, incomplete, or has multiple reasonable interpretations. Your job: ask the one question that unblocks the work.

package/.claude/commands/goal.md

@@ -0,0 +1,98 @@
+---
+description: Add or update a long-horizon goal in .bizar/PROGRESS.md — same source-of-truth as the v8 dashboard Goals view.
+---
+
+# Goal — Track a Long-Horizon Commitment
+
+You are in `/goal` mode. The user has invoked this command to add or
+update a **goal** in `.bizar/PROGRESS.md`. This file is the single
+source of truth for goals — both the v8 dashboard's Goals view and
+Claude Code's `/goal` slash command read from and write to it.
+
+## Contract
+
+- **Goals live in `.bizar/PROGRESS.md`** in the active project root.
+  Parse the current file first so you don't clobber existing goals.
+- **Round-trip via the dashboard API.** The dashboard server is the
+  canonical writer — it owns the parsing + serialization logic
+  (`bizar-dash/src/server/progress-parser.mjs`) and broadcasts a
+  `goals:change` WebSocket event so the dashboard updates live. **Do
+  not edit PROGRESS.md directly** unless the dashboard is down.
+- **Use the dashboard's HTTP API by default.** Resolve the dashboard
+  port from `~/.cache/bizarharness/dash-auth.json` (`port` field), then
+  POST/PATCH. This keeps goals in lock-step with whatever the
+  dashboard user is looking at.
+
+## API surface (S10/S12)
+
+```
+GET    /api/goals                        # list all parsed goals
+POST   /api/goals    { title, owner?, due? }   # create
+GET    /api/goals/:id                    # single goal
+PATCH  /api/goals/:id { title?, owner?, due? } # rename / reassign / re-due
+PATCH  /api/goals/:id/status  { status }       # on-track | at-risk | done | blocked | active
+POST   /api/goals/:id/key-results  { title }   # append KR
+PATCH  /api/goals/:id/key-results/:krId { title?, done? }  # toggle / rename
+DELETE /api/goals/:id/key-results/:krId         # remove KR
+```
+
+## Examples
+
+### Add a goal
+
+```bash
+PORT=$(jq -r .port ~/.cache/bizarharness/dash-auth.json)
+curl -s -X POST http://127.0.0.1:$PORT/api/goals \
+  -H "Content-Type: application/json" \
+  -d '{"title":"Ship v8 dashboard","owner":"sam","due":"2026-09-30"}'
+```
+
+### Change a goal's status to at-risk
+
+```bash
+curl -s -X PATCH http://127.0.0.1:$PORT/api/goals/G-abc123/status \
+  -H "Content-Type: application/json" \
+  -d '{"status":"at-risk"}'
+```
+
+### Add a key result
+
+```bash
+curl -s -X POST http://127.0.0.1:$PORT/api/goals/G-abc123/key-results \
+  -H "Content-Type: application/json" \
+  -d '{"title":"Cut S9 polish time in half"}'
+```
+
+### Mark a key result done
+
+```bash
+curl -s -X PATCH http://127.0.0.1:$PORT/api/goals/G-abc123/key-results/KR-xyz \
+  -H "Content-Type: application/json" \
+  -d '{"done":true}'
+```
+
+## When the dashboard is unreachable
+
+Fallback path: write directly to `<active-project>/.bizar/PROGRESS.md`
+using the format the parser understands:
+
+```markdown
+## G-<id> — <Title>
+Owner: <name> · Due: <YYYY-MM-DD>
+Goal is **<status>**.
+
+- [ ] <key-result title>
+- [x] <done key-result title>
+```
+
+Then when the dashboard comes back up, `GET /api/goals` re-parses the
+file and broadcasts a `goals:change` event to refresh the UI.
+
+## Background: why this exists
+
+`/goal` was added in S12 of the v8 dashboard rewrite. Before this,
+goals lived only in the user's head and `FINAL_GOAL.md` (which is the
+user's own planning doc, not the harness's tracker). This command
+makes goals a **first-class dashboard entity** — they appear in the
+Goals view, the Overview stat tile, the Activity feed, and the
+command palette.

package/.claude/settings.local.json

@@ -0,0 +1,7 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(claude --version)"
+    ]
+  }
+}