parsecraft 2026.9.2__tar.gz

parsecraft-2026.9.2/.agents/FILES.md

@@ -0,0 +1,37 @@
+# AGENTS.md — FILES
+
+Single source of truth for paths, config keys, and naming conventions.
+Kept compact — agents hallucinate less when they know where definitions live.
+
+## Pattern
+
+- One file owns each class of definition (paths, config defaults, enums).
+- Import from that file. Never hard-code values in other modules.
+- Variables that address files get `_file` suffix; directories get `_dir`.
+
+## Project-specific sources of truth
+
+| What                   | Where                                                           | Key names                                       |
+| ---------------------- | --------------------------------------------------------------- | ----------------------------------------------- |
+| Package source root    | `src/parsecraft/`  | `__init__.py`, `__about__.py` (version)         |
+| CLI entry points       | `src/parsecraft/cli/`            | `app.py` (Typer app), `args.py`, `commands.py`  |
+| Test suite             | `tests/`                                                        | `test_*.py`, `conftest.py`                      |
+| Issue tracker (beads)  | `.beads/`                                                       | `bd` CLI, issue prefix `pc`                     |
+| Project metadata       | `pyproject.toml`                                                | `[project]`, `[tool.pytest.ini_options]`        |
+| Linter/formatter       | `ruff.toml`                                                     | Ruff rule selection, line length                |
+| Type checker           | `ty.toml`                                                       | ty strictness                                   |
+| Markdown linter        | `.config/rumdl.toml`                                            | `line-length`, `flavor`, disabled rules         |
+| mise tasks             | `.config/mise/config.toml` + `.config/mise/conf.d/*.toml`       | `[tasks.dev]`, `[tasks.test]`, ...              |
+| Copier answers         | `.copier-answers.yml`                                           | Template version + answers (regenerated)        |
+| Pre-commit config      | `.pre-commit-config.yaml`                                       | Hook list                                       |
+| MCP server config      | `.config/mise/conf.d/mcp.toml`                                  | `[tasks.add-mcp-servers]`, tool list            |
+| Skills install task    | `.config/mise/conf.d/skills.toml`                               | `[tasks.add-skills]`, skill list                |
+
+## Naming conventions
+
+- **Repository name** (`project_slug`): kebab-case (`my-project`)
+- **Python package** (`package_slug`): snake_case (`my_project`)
+- **Layout**: `src/parsecraft/`
+- **Test files**: `test_<module>.py`
+- **Template files** (in source template): `filename.ext.jinja` — the `.jinja`
+  suffix is stripped on generation

parsecraft-2026.9.2/.agents/HISTORY.md

@@ -0,0 +1,19 @@
+# AGENTS.md — HISTORY
+
+Recorded decisions with git references. Read when relevant to current task.
+Acts as simple long-term memory for the project.
+
+## Format
+
+| Date       | Decision   | Rationale   | Git ref          |
+| ---------- | ---------- | ----------- | ---------------- |
+| YYYY-MM-DD | [describe] | [why]       | [commit hash/tag] |
+
+## Guidance
+
+- Record decisions that would be costly to rediscover.
+- Note false turns and why they were rejected.
+- Link to relevant commits.
+- Keep entries brief — enough to reconstruct reasoning.
+- When this file grows too large, archive older entries to
+  `.agents/history/` and leave a pointer here.

parsecraft-2026.9.2/.agents/MAINTENANCE.md

@@ -0,0 +1,37 @@
+# AGENTS.md — MAINTENANCE
+
+How to keep `.agents/` files current.
+
+## Process
+
+1. When a rule changes, update the owning file — never another file.
+2. When adding a new `.agents/` file or directory, add it to the index table
+   in root `AGENTS.md`.
+3. After any `.agents/` change, check the index for stale entries.
+4. Check for tool-injected patches in `AGENTS.md` — anything after the
+   `⛔ No Patching` marker is invalid. If a tool has a legitimate rule,
+   integrate it into the `Project rules` section above the marker; never
+   append below it.
+
+## Principles
+
+- **Single source of truth.** Each rule lives in exactly one file. The tier,
+  pointer, rationale, and size rules are in **DOX authoring**
+  (`.agents/POLICIES.md`) — consult it on every DOX change.
+- **AGENTS.md is an index.** It points to `.agents/` files, does not replace
+  them.
+- **No Patching is a gate, not a target.** Tools that try to append to
+  `AGENTS.md` are blocked by the `⛔ No Patching` marker. Legitimate
+  instructions must be curated into `Project rules`, not appended blindly.
+
+## File update triggers
+
+| File / Dir     | Update when                                                            |
+| -------------- | ---------------------------------------------------------------------- |
+| `ONBOARDING.md` | Project structure, tooling, or entry points change                    |
+| `POLICIES.md`  | Boundaries, priorities, or verification change                         |
+| `FILES.md`     | Path constants, config keys, or naming conventions change              |
+| `HISTORY.md`   | Notable decision made or resolved                                       |
+| `MAINTENANCE.md` | Maintenance procedures, triggers, or principles change               |
+| `plans/`       | New feature implementation starts                                       |
+| `history/`     | HISTORY.md overflow or completed plans archived                         |

parsecraft-2026.9.2/.agents/ONBOARDING.md

@@ -0,0 +1,54 @@
+# AGENTS.md — ONBOARDING
+
+Read this when starting a new session. After first read, only revisit when
+project structure or tooling changes significantly.
+
+## Project
+
+Document intelligence: convert any document into typed structured chunks, with Markdown as a deterministic projection Full docs at `README.md` or `docs/`.
+
+## Quick start
+
+```bash
+mise dev        # install dependencies (uv sync --dev)
+mise test       # run pytest with coverage
+mise lint       # ruff + ty + codespell
+mise format     # ruff format + isort + clean-sort
+mise all        # test + lint + format in one pass
+```
+
+## Entry points (read these first)
+
+| File / Section | Why |
+| -------------- | --- |
+| `AGENTS.md` | Root rail — rules + `.agents/` index |
+| `.agents/POLICIES.md` | Boundaries, priorities, verification |
+| `.agents/FILES.md` | Source-of-truth locations for this package |
+| `pyproject.toml` | Dependencies, pytest config, build backend |
+| `.copier-answers.yml` | Template answers (regenerated on `copier update`) |
+
+## Layout
+
+- **`src/parsecraft/`** — primary package source (src layout)
+- **`tests/`** — pytest suite (100% coverage gate)
+- **`src/parsecraft/cli/`** — Typer CLI
+- **`docs/`** — Zensical / MkDocs Material documentation
+- **`.config/mise/`** — task runner config (`config.toml` + `conf.d/` fragments)
+
+## Where to dig deeper
+
+- `docs/` — user-facing documentation
+- `.agents/HISTORY.md` — past decisions and rationale
+- Source-tree AGENTS.md files — local contracts for each area
+
+## Available tools
+
+If MCP dev-features are enabled (`include_mcp_tasks`), the following may be
+available after running `mise run add-mcp-servers <agent>` and `mise run
+add-skills`:
+
+- **repowise** — architecture overview, risk, health scores, change-risk
+- **codegraph** — symbol search, call graphs, dependency maps
+- **grepai** — semantic code search by meaning, not text
+- **bd / beads** — distributed issue tracker (if `tracking` skill category enabled)
+- Various slop/dead-code detectors (see `.config/mise/conf.d/skills.toml`)

parsecraft-2026.9.2/.agents/POLICIES.md

@@ -0,0 +1,127 @@
+# AGENTS.md — POLICIES
+
+Always applicable. Boundaries, priorities, verification, checklist.
+
+## Priorities
+
+1. Correctness
+2. Evidence
+3. Safety
+4. Minimal changes
+5. Consistency
+6. Performance
+
+## Boundaries
+
+- NEVER fabricate paths, commits, APIs, config keys, env vars, test results,
+  or benchmark numbers. If you don't know, say so.
+- NEVER guess at command names, flags, or paths. Read source or run `--help`.
+- NEVER add secrets, API keys, or tokens to files. Use env vars.
+- NEVER run destructive commands (`rm -rf`, `git reset --hard`,
+  `git push --force`) without explicit confirmation.
+- NEVER delete or move files without explicit instruction.
+- NEVER create temp files in project root. Use dedicated temp dir.
+
+## Change constraints
+
+- Minimal, surgical edits. Preserve existing style.
+- No new dependencies without explicit instruction.
+- No unrelated refactoring while fixing a bug.
+
+## Code quality
+
+Universal defaults. Project-specific standards live in child AGENTS.md.
+
+- **SRP** — one reason to change per module/function.
+- **DRY** — check before adding. Extract on third occurrence (Rule of Three).
+- **Redundant code** — remove dead branches, unreachable conditions, unused
+  params/imports before finishing.
+- **Duplication vs. abstraction** — prefer duplication over wrong premature
+  abstraction.
+- No new code-quality tooling by default — opt in per project.
+
+## Completion checklist
+
+- Change solves the stated problem
+- Relevant validation ran (or gaps stated)
+- No unintended side effects or secrets exposed
+
+## DOX authoring (keep AGENTS.md lean)
+
+AGENTS.md and `.agents/` files share limited context. Bloat and duplication
+are the failure mode.
+
+### Where a rule lives
+
+A rule goes in the **highest (most general) tier that fully applies**:
+
+- Applies to **all code in the project** → `.agents/POLICIES.md` (default).
+- Meaningful **only inside one subtree** → that subtree's `AGENTS.md`.
+- Just helps navigation → the parent's Child DOX Index, nothing else.
+
+### Reference, don't restate
+
+A rule appears in **exactly one file**. Other files use a **pointer line**:
+`<topic> — see <file>`. Never copy the rule, rationale, or example.
+
+### Rule first, rationale second, never third
+
+A DOX line is the rule. If a rationale is costly to rediscover, add one
+short clause. No multi-paragraph explanations or code pairs — those belong
+in a skill or `docs/`, linked once.
+
+### Content rules
+
+- **No tree views.** Generate on demand with `rg --files | tree-cli --fromfile`.
+- **No history in AGENTS.md files.** Git log has routine history. Record only
+  decisions costly to rediscover — in `.agents/HISTORY.md` (or
+  `.agents/history/` for overflow archives). See **Implementation Plans**
+  below for archiving completed plans.
+- **No TODO lists.** Use issue trackers or beads.
+
+## Implementation Plans
+
+- Plans, refactoring plans, and design docs go in `.agents/plans/<feature>/`
+  — NOT under version control (gitignored).
+- Name descriptively with phase-number prefixes so file order matches
+  implementation order, e.g. `01-sub-feature.md`, `02-next-sub-feature.md`.
+- NEVER commit plans to git. They are mutable working artifacts.
+- Shipped docs (user-facing guides, API references) go in `docs/` and
+  ARE committed.
+
+## Documentation
+
+- When `.agents/HISTORY.md` grows too large, archive older entries to
+  `.agents/history/`. Reference them from `.agents/HISTORY.md`.
+- Completed plans (`.agents/plans/<feature>/`) may be archived to
+  `.agents/history/<feature>/` for long-term reference.
+- `.agents/history/` IS version-controlled (durable decision records).
+
+## Size budget
+
+- `.agents/` files: ≤ **120 lines** (always-injected context).
+- Subtree `AGENTS.md`: ≤ **250 lines** (loaded cumulatively with parents).
+
+Exceeding the budget signals restating instead of pointing, or hoarding
+rationale. Cut first; split the subtree only as a last resort.
+
+## Verification
+
+```bash
+mise all        # test + lint + format (composite task)
+mise test       # pytest with coverage gate (100%)
+mise lint       # ruff + ty + codespell
+mise format     # ruff format + isort + clean-sort
+mise format-md  # rumdl over docs/, .agents/, ./ (Markdown only)
+```
+
+Pre-commit hooks (`.pre-commit-config.yaml`) run a subset of the above on every
+commit. Run `pre-commit run --all-files` to check the whole tree.
+
+## Response format
+
+Concise and specific. No filler, intros, or restated requirements.
+Answer direct questions directly.
+
+For review/debugging/analysis: findings with references, conclusion,
+approach. Mention caveats.

parsecraft-2026.9.2/.beads/.gitignore

@@ -0,0 +1,81 @@
+# Dolt database (managed by Dolt, not git)
+dolt/
+embeddeddolt/
+proxieddb/
+
+# Runtime files
+bd.sock
+bd.sock.startlock
+sync-state.json
+last-touched
+.exclusive-lock
+
+# Daemon runtime (lock, log, pid)
+daemon.*
+
+# 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
+
+proxied_server_client_info.json
+
+# 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
+
+# Workspace operation gate (internal/workspacegate): physical-root gate
+# files live beside the guarded root inside .beads (e.g. dolt.gate.lock)
+*.gate.lock*
+export-state/
+export-state.json
+last_pull
+
+# 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
+
+# Debug-mode pprof artifacts (written when dolt.debug: true in config.yaml)
+dolt-pprof/
+
+# Corrupt backup directories (created by bd doctor --fix recovery)
+*.corrupt.backup/
+
+# Backup data (auto-exported JSONL, local-only)
+backup/
+
+# 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.

parsecraft-2026.9.2/.beads/README.md

@@ -0,0 +1,85 @@
+# 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
+- **Sync-ready**: Uses Dolt remotes for backup and team sharing
+
+## 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**
+
+- Dolt-native sync via bd dolt push / bd dolt pull
+- 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* ⚡

parsecraft-2026.9.2/.beads/config.yaml

@@ -0,0 +1,74 @@
+# 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, .beads/issues.jsonl is the only local store
+# 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: ""
+
+# Optional JSONL sidecar for explicit agent/tool interaction audit records.
+# Issue history is always recorded in the database and is visible with
+# bd history <id> --events; this only controls .beads/interactions.jsonl.
+# audit:
+#   enabled: false
+
+# 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
+
+# Dolt-native backup (periodic backup for off-machine recovery)
+# This is full database backup only. Cross-machine sync uses Dolt remotes.
+# backup:
+#   enabled: false     # Disable auto-backup entirely
+#   interval: 15m      # Minimum time between auto-backups
+#   git-push: false    # Disable git push (backup locally only)
+#   git-repo: ""       # Separate git repo for backups (default: project repo)
+
+# Optional JSONL auto-export for viewers, interchange, and issue-level migration.
+# Disabled by default; enable only when an integration needs fresh .beads/issues.jsonl.
+# Use relative paths under .beads/ for JSONL import/export filenames.
+# export:
+#   auto: false
+#   path: issues.jsonl
+#   interval: 60s
+#   git-add: false
+# import:
+#   path: issues.jsonl
+
+# Integration settings (access with 'bd config get/set')
+# Non-secret keys (stored in the database):
+# - jira.url, jira.project
+# - linear.team_id
+# - github.org, github.repo
+#
+# Secret keys (stored in this file but prefer env vars to avoid git exposure):
+# - linear.api_key  → use LINEAR_API_KEY env var instead
+# - github.token    → use GITHUB_TOKEN env var instead
+
+sync.remote: "git+https://github.com/jr2804/parsecraft.git"

parsecraft-2026.9.2/.beads/hooks/post-checkout

@@ -0,0 +1,59 @@
+#!/usr/bin/env sh
+# --- BEGIN BEADS INTEGRATION v1.3.0 ---
+# This section is managed by beads. Do not remove these markers.
+if command -v bd >/dev/null 2>&1; then
+  export BD_GIT_HOOK=1
+  _bd_timeout=${BEADS_HOOK_TIMEOUT:-300}
+  case "$_bd_timeout" in
+    *[!0-9]*|'') _bd_timeout_invalid=1 ;;
+    *[1-9]*) _bd_timeout_invalid=0 ;;
+    *) _bd_timeout_invalid=1 ;;
+  esac
+  if [ "$_bd_timeout_invalid" -eq 1 ]; then
+    echo >&2 "beads: invalid BEADS_HOOK_TIMEOUT; using 300 seconds"
+    _bd_timeout=300
+  fi
+  _bd_timeout_backend=none
+  _bd_timeout_command=
+  for _bd_timeout_candidate in timeout gtimeout; do
+    if command -v "$_bd_timeout_candidate" >/dev/null 2>&1; then
+      if _bd_timeout_version="$("$_bd_timeout_candidate" --version 2>/dev/null)"; then
+        case "$_bd_timeout_version" in
+          "timeout (GNU coreutils) "*) _bd_timeout_command=$_bd_timeout_candidate; break ;;
+        esac
+      fi
+    fi
+  done
+  if [ -n "$_bd_timeout_command" ]; then
+    _bd_timeout_backend=coreutils
+    if "$_bd_timeout_command" -- "$_bd_timeout" bd hooks run post-checkout "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  elif command -v perl >/dev/null 2>&1; then
+    _bd_timeout_backend=perl
+    if perl -e 'alarm shift; exec @ARGV' -- "$_bd_timeout" bd hooks run post-checkout "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  else
+    echo >&2 "beads: hook 'post-checkout' running without timeout; install coreutils or perl to enable BEADS_HOOK_TIMEOUT"
+    if bd hooks run post-checkout "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  fi
+  if { [ "$_bd_timeout_backend" = coreutils ] && [ "$_bd_exit" -eq 124 ]; } || { [ "$_bd_timeout_backend" = perl ] && [ "$_bd_exit" -eq 142 ]; }; then
+    echo >&2 "beads: hook 'post-checkout' timed out after ${_bd_timeout}s — continuing without beads"
+    _bd_exit=0
+  fi
+  if [ "$_bd_exit" -eq 3 ]; then
+    echo >&2 "beads: database not initialized — skipping hook 'post-checkout'"
+    _bd_exit=0
+  fi
+  if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
+fi
+# --- END BEADS INTEGRATION v1.3.0 ---

parsecraft-2026.9.2/.beads/hooks/post-merge

@@ -0,0 +1,59 @@
+#!/usr/bin/env sh
+# --- BEGIN BEADS INTEGRATION v1.3.0 ---
+# This section is managed by beads. Do not remove these markers.
+if command -v bd >/dev/null 2>&1; then
+  export BD_GIT_HOOK=1
+  _bd_timeout=${BEADS_HOOK_TIMEOUT:-300}
+  case "$_bd_timeout" in
+    *[!0-9]*|'') _bd_timeout_invalid=1 ;;
+    *[1-9]*) _bd_timeout_invalid=0 ;;
+    *) _bd_timeout_invalid=1 ;;
+  esac
+  if [ "$_bd_timeout_invalid" -eq 1 ]; then
+    echo >&2 "beads: invalid BEADS_HOOK_TIMEOUT; using 300 seconds"
+    _bd_timeout=300
+  fi
+  _bd_timeout_backend=none
+  _bd_timeout_command=
+  for _bd_timeout_candidate in timeout gtimeout; do
+    if command -v "$_bd_timeout_candidate" >/dev/null 2>&1; then
+      if _bd_timeout_version="$("$_bd_timeout_candidate" --version 2>/dev/null)"; then
+        case "$_bd_timeout_version" in
+          "timeout (GNU coreutils) "*) _bd_timeout_command=$_bd_timeout_candidate; break ;;
+        esac
+      fi
+    fi
+  done
+  if [ -n "$_bd_timeout_command" ]; then
+    _bd_timeout_backend=coreutils
+    if "$_bd_timeout_command" -- "$_bd_timeout" bd hooks run post-merge "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  elif command -v perl >/dev/null 2>&1; then
+    _bd_timeout_backend=perl
+    if perl -e 'alarm shift; exec @ARGV' -- "$_bd_timeout" bd hooks run post-merge "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  else
+    echo >&2 "beads: hook 'post-merge' running without timeout; install coreutils or perl to enable BEADS_HOOK_TIMEOUT"
+    if bd hooks run post-merge "$@"; then
+      _bd_exit=0
+    else
+      _bd_exit=$?
+    fi
+  fi
+  if { [ "$_bd_timeout_backend" = coreutils ] && [ "$_bd_exit" -eq 124 ]; } || { [ "$_bd_timeout_backend" = perl ] && [ "$_bd_exit" -eq 142 ]; }; then
+    echo >&2 "beads: hook 'post-merge' timed out after ${_bd_timeout}s — continuing without beads"
+    _bd_exit=0
+  fi
+  if [ "$_bd_exit" -eq 3 ]; then
+    echo >&2 "beads: database not initialized — skipping hook 'post-merge'"
+    _bd_exit=0
+  fi
+  if [ "$_bd_exit" -ne 0 ]; then exit "$_bd_exit"; fi
+fi
+# --- END BEADS INTEGRATION v1.3.0 ---