syntaur 0.1.14 → 0.2.0

package/dashboard/dist/assets/stateDiagram-v2-FVOUBMTO--yuSBnLh.js

@@ -1 +0,0 @@
-import{s as e,b as r,a,S as s}from"./chunk-NQ4KR5QH-BFBu1fmg.js";import{_ as i}from"./mermaid.core-DyEs-LPd.js";import"./chunk-55IACEB6-B3vP9Psg.js";import"./chunk-KX2RTZJC-DnGsx5jo.js";import"./index-CEMjexkj.js";var p={parser:a,get db(){return new s(2)},renderer:r,styles:e,init:i(t=>{t.state||(t.state={}),t.state.arrowMarkerAbsolute=t.arrowMarkerAbsolute},"init")};export{p as diagram};

package/examples/sample-mission/agent.md

@@ -1,33 +0,0 @@
----
-mission: build-auth-system
-updated: "2026-03-15T09:00:00Z"
----
-
-# Agent Instructions
-
-All agents working on the auth system must follow these guidelines. These apply regardless of which agent framework you are using.
-
-## Conventions
-
-- Language: TypeScript (strict mode enabled)
-- Runtime: Node.js 20
-- Database: PostgreSQL 16 with the `pg` driver (no ORM)
-- Authentication: JWT with RS256 signing algorithm
-- Password hashing: bcrypt with cost factor 12
-- Use named exports, not default exports
-- All database queries must use parameterized statements (no string interpolation)
-- Error responses follow the format: `{ error: string, code: string }`
-
-## Boundaries
-
-- Do not modify the `infrastructure/` directory — deployment config is managed separately
-- Do not install additional database drivers or ORMs
-- Do not change the JWT signing algorithm without filing a decision record
-- All schema migrations must be backward-compatible
-- Never store plaintext passwords or secrets in code
-
-## Resources
-
-- [Auth Requirements](./resources/auth-requirements.md) — functional and security requirements
-- PostgreSQL 16 docs: https://www.postgresql.org/docs/16/
-- JWT RFC 7519: https://datatracker.ietf.org/doc/html/rfc7519

package/examples/sample-mission/claude.md

@@ -1,13 +0,0 @@
-# Claude Code Instructions — build-auth-system
-
-Read `agent.md` first for universal conventions and boundaries.
-
-## Additional Claude Code Rules
-
-- When creating new files, always add them to the appropriate barrel export (`index.ts`)
-- Run `npm run typecheck` after making changes to catch type errors early
-- Use `npm test -- --watch` during development for fast feedback
-- Prefer explicit type annotations on function signatures over inference
-- When writing SQL migrations, name files with sequential numbering: `001_create_users.sql`, `002_create_sessions.sql`, etc.
-- Commit frequently with descriptive messages referencing the assignment slug
-- If you encounter a question you cannot resolve from existing context, add it to the Q&A section of your assignment.md and continue working on other tasks — the unanswered question will surface through `_status.md` needsAttention. Do NOT set status to `blocked` for unanswered questions; `blocked` is reserved for hard runtime/manual blockers.

package/platforms/claude-code/skills/create-mission/SKILL.md

@@ -1,51 +0,0 @@
----
-name: create-mission
-description: Create a new Syntaur mission with all scaffolding files (manifest, agent instructions, indexes)
-argument-hint: <title> [--slug <slug>] [--dir <path>] [--workspace <workspace>]
-allowed-tools:
-  - Bash
-  - Read
----
-
-# Create Mission
-
-Create a new Syntaur mission from within Claude Code.
-
-## Arguments
-
-The user provided: $ARGUMENTS
-
-Parse the arguments:
-- First argument (required): the mission title (e.g., `"Build Auth System"`)
-- `--slug` (optional): override the auto-generated slug
-- `--dir` (optional): override the default mission directory
-- `--workspace` (optional): workspace grouping label (e.g., `syntaur`, `reeva`)
-
-If no title was provided, ask the user what the mission should be called.
-
-## Step 1: Run the CLI
-
-Build the command from the parsed arguments. Use `dangerouslyDisableSandbox: true` since the CLI writes to `~/.syntaur/` which is outside the project sandbox.
-
-```bash
-syntaur create-mission "<title>" [--slug <slug>] [--dir <path>] [--workspace <workspace>]
-```
-
-If the command fails (e.g., slug collision, empty title), report the error and suggest fixes.
-
-## Step 2: Read the Created Mission
-
-After successful creation, extract the mission slug and directory from the CLI output. Read the generated `mission.md` to confirm the structure:
-
-```bash
-cat ~/.syntaur/missions/<slug>/mission.md
-```
-
-## Step 3: Guide Next Steps
-
-Tell the user:
-- The mission was created with its slug and location
-- List the key files created (manifest.md, mission.md, agent.md, claude.md)
-- Suggest they edit `mission.md` to fill in the goal, scope, and context sections
-- Suggest they edit `agent.md` to set conventions and boundaries for agents
-- Suggest running `/create-assignment` to add assignments to this mission

package/platforms/codex/skills/create-mission/SKILL.md

@@ -1,35 +0,0 @@
----
-name: create-mission
-description: Use when the user wants to create a new Syntaur mission and scaffold its mission.md, agent.md, claude.md, indexes, and manifest files.
----
-
-# Create Mission
-
-Create a new Syntaur mission from Codex.
-
-## Arguments
-
-User arguments: `$ARGUMENTS`
-
-Parse:
-
-- First positional argument: mission title
-- `--slug <slug>` optional
-- `--dir <path>` optional
-- `--workspace <workspace>` optional: workspace grouping label (e.g., `syntaur`, `reeva`)
-
-If no title was provided, ask the user for it.
-
-## Workflow
-
-1. Run `syntaur create-mission "<title>" [--slug <slug>] [--dir <path>] [--workspace <workspace>]`.
-2. If the command fails, report the error and stop.
-3. Read the generated `mission.md` to confirm the mission path and scaffold.
-4. Summarize:
-   - mission slug
-   - mission directory
-   - key files created: `manifest.md`, `mission.md`, `agent.md`, `claude.md`
-5. Suggest next steps:
-   - fill in `mission.md`
-   - add mission-wide guidance to `agent.md`
-   - run `create-assignment` for the first task