sase 0.1.0__tar.gz

sase-0.1.0/.beads/.gitignore

@@ -0,0 +1,52 @@
+# SQLite databases
+*.db
+*.db?*
+*.db-journal
+*.db-wal
+*.db-shm
+
+# Daemon runtime files
+daemon.lock
+daemon.log
+daemon-*.log.gz
+daemon.pid
+bd.sock
+sync-state.json
+last-touched
+
+# Local version tracking (prevents upgrade notification spam after git ops)
+.local_version
+
+# Legacy database files
+db.sqlite
+bd.db
+
+# Worktree redirect file (contains relative path to main repo's .beads/)
+# Must not be committed as paths would be wrong in other clones
+redirect
+
+# Merge artifacts (temporary files from 3-way merge)
+beads.base.jsonl
+beads.base.meta.json
+beads.left.jsonl
+beads.left.meta.json
+beads.right.jsonl
+beads.right.meta.json
+
+# Sync state (local-only, per-machine)
+# These files are machine-specific and should not be shared across clones
+.sync.lock
+.jsonl.lock
+sync_base.jsonl
+export-state/
+
+# Dolt database (managed by Dolt remotes, not git)
+dolt/
+dolt-access.lock
+dolt.*.corrupt.backup/
+
+# NOTE: Do NOT add negation patterns (e.g., !issues.jsonl) here.
+# They would override fork protection in .git/info/exclude, allowing
+# contributors to accidentally commit upstream issue databases.
+# The JSONL files (issues.jsonl, interactions.jsonl) and config files
+# are tracked by git by default since no pattern above ignores them.

sase-0.1.0/.beads/PRIME.md

@@ -0,0 +1,86 @@
+# Beads Workflow Context
+
+> **Context Recovery**: Run `sase_bd prime` after compaction, clear, or new session Hooks auto-call this in Claude Code
+> when .beads/ detected
+
+> **Important**: Always use `sase_bd` (at `tools/sase_bd`) instead of `bd` directly.
+
+# Session Close Protocol
+
+Before wrapping up, run `sase_bd sync` to ensure beads data is flushed to JSONL.
+
+**Do NOT commit or push code changes.** The stop hook handles commit prompting — it runs quality checks and then asks
+you to use the `/commit` skill if there are uncommitted changes.
+
+## Core Rules
+
+- **Default**: Use beads for ALL task tracking (`sase_bd create`, `sase_bd ready`, `sase_bd close`)
+- **Prohibited**: Do NOT use TodoWrite, TaskCreate, or markdown files for task tracking
+- **Workflow**: Create beads issue BEFORE writing code, mark in_progress when starting
+- Persistence you don't need beats lost context
+- Git workflow: hooks auto-sync, run `sase_bd sync` at session end
+- Session management: check `sase_bd ready` for available work
+
+## Essential Commands
+
+### Finding Work
+
+- `sase_bd ready` - Show issues ready to work (no blockers)
+- `sase_bd list --status=open` - All open issues
+- `sase_bd list --status=in_progress` - Your active work
+- `sase_bd show <id>` - Detailed issue view with dependencies
+
+### Creating & Updating
+
+- `sase_bd create --title="..." --type=task|bug|feature --priority=2` - New issue
+  - Priority: 0-4 or P0-P4 (0=critical, 2=medium, 4=backlog). NOT "high"/"medium"/"low"
+- `sase_bd update <id> --status=in_progress` - Claim work
+- `sase_bd update <id> --assignee=username` - Assign to someone
+- `sase_bd update <id> --title/--description/--notes/--design` - Update fields inline
+- `sase_bd close <id>` - Mark complete
+- `sase_bd close <id1> <id2> ...` - Close multiple issues at once (more efficient)
+- `sase_bd close <id> --reason="explanation"` - Close with reason
+- **Tip**: When creating multiple issues/tasks/epics, use parallel subagents for efficiency
+- **WARNING**: Do NOT use `sase_bd edit` - it opens $EDITOR (vim/nano) which blocks agents
+
+### Dependencies & Blocking
+
+- `sase_bd dep add <issue> <depends-on>` - Add dependency (issue depends on depends-on)
+- `sase_bd blocked` - Show all blocked issues
+- `sase_bd show <id>` - See what's blocking/blocked by this issue
+
+### Sync & Collaboration
+
+- `sase_bd sync` - Sync with git remote (run at session end)
+- `sase_bd sync --status` - Check sync status without syncing
+
+### Project Health
+
+- `sase_bd stats` - Project statistics (open/closed/blocked counts)
+- `sase_bd doctor` - Check for issues (sync problems, missing hooks)
+
+## Common Workflows
+
+**Starting work:**
+
+```bash
+sase_bd ready           # Find available work
+sase_bd show <id>       # Review issue details
+sase_bd update <id> --status=in_progress  # Claim it
+```
+
+**Completing work:**
+
+```bash
+sase_bd close <id1> <id2> ...    # Close all completed issues at once
+sase_bd sync                     # Push to remote
+```
+
+**Creating dependent work:**
+
+```bash
+# Run sase_bd create commands in parallel (use subagents for many items)
+sase_bd create --title="Implement feature X" --type=feature
+sase_bd create --title="Write tests for X" --type=task
+sase_bd dep add beads-yyy beads-xxx  # Tests depend on Feature (Feature blocks tests)
+```

sase-0.1.0/.beads/README.md

@@ -0,0 +1,87 @@
+# Beads - AI-Native Issue Tracking
+
+Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly
+in your codebase alongside your code.
+
+## What is Beads?
+
+Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their
+issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
+
+**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
+
+## Quick Start
+
+### Essential Commands
+
+```bash
+# Create new issues
+bd create "Add user authentication"
+
+# View all issues
+bd list
+
+# View issue details
+bd show <issue-id>
+
+# Update issue status
+bd update <issue-id> --status in_progress
+bd update <issue-id> --status done
+
+# Sync with git remote
+bd sync
+```
+
+### Working with Issues
+
+Issues in Beads are:
+
+- **Git-native**: Stored in `.beads/issues.jsonl` and synced like code
+- **AI-friendly**: CLI-first design works perfectly with AI coding agents
+- **Branch-aware**: Issues can follow your branch workflow
+- **Always in sync**: Auto-syncs with your commits
+
+## Why Beads?
+
+✨ **AI-Native Design**
+
+- Built specifically for AI-assisted development workflows
+- CLI-first interface works seamlessly with AI coding agents
+- No context switching to web UIs
+
+🚀 **Developer Focused**
+
+- Issues live in your repo, right next to your code
+- Works offline, syncs when you push
+- Fast, lightweight, and stays out of your way
+
+🔧 **Git Integration**
+
+- Automatic sync with git commits
+- Branch-aware issue tracking
+- Intelligent JSONL merge resolution
+
+## Get Started with Beads
+
+Try Beads in your own projects:
+
+```bash
+# Install Beads
+curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
+
+# Initialize in your repo
+bd init
+
+# Create your first issue
+bd create "Try out Beads"
+```
+
+## Learn More
+
+- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
+- **Quick Start Guide**: Run `bd quickstart`
+- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
+
+---
+
+_Beads: Issue tracking that moves at the speed of thought_ ⚡

sase-0.1.0/.beads/config.yaml

@@ -0,0 +1,67 @@
+# Beads Configuration File
+# This file configures default behavior for all bd commands in this repository
+# All settings can also be set via environment variables (BD_* prefix)
+# or overridden with command-line flags
+
+# Issue prefix for this repository (used by bd init)
+# If not set, bd init will auto-detect from directory name
+# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
+# issue-prefix: ""
+
+# Use no-db mode: load from JSONL, no SQLite, write back after each command
+# When true, bd will use .beads/issues.jsonl as the source of truth
+# instead of SQLite database
+# no-db: false
+
+# Disable daemon for RPC communication (forces direct database access)
+# no-daemon: false
+
+# Disable auto-flush of database to JSONL after mutations
+# no-auto-flush: false
+
+# Disable auto-import from JSONL when it's newer than database
+# no-auto-import: false
+
+# Enable JSON output by default
+# json: false
+
+# Default actor for audit trails (overridden by BD_ACTOR or --actor)
+# actor: ""
+
+# Path to database (overridden by BEADS_DB or --db)
+# db: ""
+
+# Auto-start daemon if not running (can also use BEADS_AUTO_START_DAEMON)
+# auto-start-daemon: true
+
+# Debounce interval for auto-flush (can also use BEADS_FLUSH_DEBOUNCE)
+# flush-debounce: "5s"
+
+# Export events (audit trail) to .beads/events.jsonl on each flush/sync
+# When enabled, new events are appended incrementally using a high-water mark.
+# Use 'bd export --events' to trigger manually regardless of this setting.
+# events-export: false
+
+# Git branch for beads commits (bd sync will commit to this branch)
+# IMPORTANT: Set this for team projects so all clones use the same sync branch.
+# This setting persists across clones (unlike database config which is gitignored).
+# Can also use BEADS_SYNC_BRANCH env var for local override.
+# If not set, bd sync will require you to run 'bd config set sync.branch <branch>'.
+# sync-branch: "beads-sync"
+
+# Multi-repo configuration (experimental - bd-307)
+# Allows hydrating from multiple repositories and routing writes to the correct JSONL
+# repos:
+#   primary: "."  # Primary repo (where this database lives)
+#   additional:   # Additional repos to hydrate from (read-only)
+#     - ~/beads-planning  # Personal planning repo
+#     - ~/work-planning   # Work planning repo
+
+# Integration settings (access with 'bd config get/set')
+# These are stored in the database, not in this file:
+# - jira.url
+# - jira.project
+# - linear.url
+# - linear.api-key
+# - github.org
+# - github.repo