stream_weaver 0.3.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 27698ae0fafbcbb9fbbea4b2f18f2215b43fc13e8c04acfe0b01a6bec722ab3c
+  data.tar.gz: 43b573368d680cd1c663b8e8c8935e883db51dd605cd25434424f94be2d19c29
+SHA512:
+  metadata.gz: 2035acdd6c8d7c98111b67ac8c3e6f3df008440cdf61072ac65749395b78c0ee05f63f9c80ec901c4e9496afe445e5edaeca4e3164600ba37513a61d85356dfb
+  data.tar.gz: '080f167accb1d0244c7bab518f236e3ddd4ddc04066abe23b2a8459fc36be8631096e863eb5820256cef5ecd72471e4342e51cafa1041ce889f2c09ca23ac6de'

data/.beads/.gitignore

@@ -0,0 +1,77 @@
+# Dolt database (managed by Dolt, not git)
+dolt/
+embeddeddolt/
+
+# Runtime files
+bd.sock
+bd.sock.startlock
+sync-state.json
+last-touched
+.exclusive-lock
+
+# Daemon runtime (lock, log, pid)
+daemon.*
+
+# Interactions log (runtime, not versioned)
+interactions.jsonl
+
+# Push state (runtime, per-machine)
+push-state.json
+
+# Lock files (various runtime locks)
+*.lock
+
+# Credential key (encryption key for federation peer auth — never commit)
+.beads-credential-key
+
+# Local version tracking (prevents upgrade notification spam after git ops)
+.local_version
+
+# Worktree redirect file (contains relative path to main repo's .beads/)
+# Must not be committed as paths would be wrong in other clones
+redirect
+
+# Sync state (local-only, per-machine)
+# These files are machine-specific and should not be shared across clones
+.sync.lock
+export-state/
+export-state.json
+
+# Ephemeral store (SQLite - wisps/molecules, intentionally not versioned)
+ephemeral.sqlite3
+ephemeral.sqlite3-journal
+ephemeral.sqlite3-wal
+ephemeral.sqlite3-shm
+
+# Dolt server management (auto-started by bd)
+dolt-server.pid
+dolt-server.log
+dolt-server.lock
+dolt-server.port
+dolt-server.activity
+
+# Corrupt backup directories (created by bd doctor --fix recovery)
+*.corrupt.backup/
+
+# Backup data (auto-exported JSONL, local-only)
+backup/
+
+# Issue state — managed in Dolt (the source of truth), not in git.
+# Auto-staged by bd hooks; ignoring it keeps feature commits clean.
+issues.jsonl
+
+# Per-project environment file (Dolt connection config, GH#2520)
+.env
+
+# Legacy files (from pre-Dolt versions)
+*.db
+*.db?*
+*.db-journal
+*.db-wal
+*.db-shm
+db.sqlite
+bd.db
+# NOTE: Do NOT add negation patterns here.
+# They would override fork protection in .git/info/exclude.
+# Config files (metadata.json, config.yaml) are tracked by git by default
+# since no pattern above ignores them.

data/.beads/README.md

@@ -0,0 +1,81 @@
+# 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> --claim
+bd update <issue-id> --status done
+
+# Sync with Dolt remote
+bd dolt push
+```
+
+### Working with Issues
+
+Issues in Beads are:
+- **Git-native**: Stored in Dolt database with version control and branching
+- **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
+- Dolt-native three-way 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* ⚡

data/.beads/config.yaml

@@ -0,0 +1,54 @@
+# 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: JSONL-only, no Dolt database
+# When true, bd will use .beads/issues.jsonl as the source of truth
+# no-db: false
+
+# Enable JSON output by default
+# json: false
+
+# Feedback title formatting for mutating commands (create/update/close/dep/edit)
+# 0 = hide titles, N > 0 = truncate to N characters
+# output:
+#   title-length: 255
+
+# Default actor for audit trails (overridden by BEADS_ACTOR or --actor)
+# actor: ""
+
+# 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
+
+# Multi-repo configuration (experimental - bd-307)
+# Allows hydrating from multiple repositories and routing writes to the correct database
+# 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
+
+# JSONL backup (periodic export for off-machine recovery)
+# Auto-enabled when a git remote exists. Override explicitly:
+# backup:
+#   enabled: false     # Disable auto-backup entirely
+#   interval: 15m      # Minimum time between auto-exports
+#   git-push: false    # Disable git push (export locally only)
+#   git-repo: ""       # Separate git repo for backups (default: project 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

data/.beads/metadata.json

@@ -0,0 +1,7 @@
+{
+  "database": "dolt",
+  "backend": "dolt",
+  "dolt_mode": "embedded",
+  "dolt_database": "stream_weaver",
+  "project_id": "943d45dd-3988-482e-9d86-2e7cfe2bb504"
+}

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/AGENTS.md

@@ -0,0 +1,91 @@
+# Agent Instructions
+
+## Tyrion is authoritative for new work
+
+StreamWeaver uses **Tyrion** as the source of truth for all new stories, discoveries,
+plans, claims, gates, and completion evidence.
+
+At session start or after compaction:
+
+```bash
+tyrion prime
+tyrion status
+```
+
+Before implementation, read the project and epic context, then claim exactly one story:
+
+```bash
+tyrion project show
+tyrion epic show
+tyrion claim-next                 # resume-safe: re-adopts your lane's in-flight story
+# or: tyrion start <story-slug>   # when the user named a specific story
+tyrion resume <story-slug>
+```
+
+Use the `tyrion-implement` skill for the full implementation loop. Record plans,
+progress, discoveries, criterion evidence, pre-push/UAT gates, and completion in
+Tyrion as the skill directs. New work is added through a reviewed feature/story flow
+(`tyrion-add-story`, `tyrion-shape` + `tyrion-import`, or an equivalent reviewed
+`.feature` update), never through an ad-hoc TODO list or another tracker.
+
+Do not query Tyrion's SQLite database directly. Use the CLI. If a required read is not
+available through the CLI, record that as a Tyrion discovery rather than coupling code
+or agent instructions to the internal schema.
+
+## Beads is a legacy backlog only
+
+Historical unresolved Beads items remain available so they can be understood and
+closed. Beads is **not** a source for selecting, claiming, or creating new work.
+
+Allowed for existing issue IDs only:
+
+```bash
+bd list --status=open
+bd search "<term>"
+bd show <existing-id>
+bd update <existing-id> ...
+bd close <existing-id> --reason="<resolution or Tyrion replacement>"
+```
+
+Never run `bd create`, `bd ready`, `bd update --claim`, or `bv` to choose new work.
+When an existing Beads item still matters, create/reuse a Tyrion story or discovery,
+link the old Beads ID in a Tyrion note, then close the legacy item when resolved.
+
+## Git and session completion
+
+- Stage explicit paths only. Never use `git add -A`, `git add .`, or `git add -u`.
+- Run the quality gate required by the active Tyrion story and record every gate run.
+- Do not commit until the story's required criterion evidence is recorded.
+- Close or checkpoint the Tyrion story before ending the session.
+- Push completed work to the remote; verify `git status` reports the branch is up to date.
+- Existing unrelated/untracked files belong to other work. Do not stage, delete, or rewrite them.
+
+## Non-interactive shell commands
+
+Always use non-interactive flags for commands that may prompt:
+
+```bash
+cp -f source dest
+mv -f source dest
+rm -f file
+rm -rf directory
+cp -rf source dest
+```
+
+- `scp`: use `-o BatchMode=yes`
+- `ssh`: use `-o BatchMode=yes`
+- `apt-get`: use `-y`
+- `brew`: use `HOMEBREW_NO_AUTO_UPDATE=1`
+
+## UKF — Universal Knowledge Facade
+
+Search the federation before researching or re-deriving durable knowledge:
+
+```bash
+uregistry list --kind wiki
+ukf search "<term>"
+```
+
+Read the returned source before proposing a duplicate design. File durable research,
+decisions, and reusable patterns in the appropriate UKF member. Keep verified records,
+proposals, and user decisions visibly distinct.