03c1c5edcf
39.5 concluded the exact CP-SAT seeder beats greedy (harbor 102 -> 92, maple 156 -> 154). Re-checked because fdp made the arms deterministic and 3qj made the model 7.5x slower. Three findings. A live bug in the cap, found on the way. solve_room_labels sets a deterministic work-unit budget (4.0) and a wall-clock backstop, commented as "a pathological-case backstop only". At 2.0s it had become THE BINDING CONSTRAINT: 2 of 24 harbor solves returned FEASIBLE not OPTIMAL, wall time hit exactly 2010 ms, and the deterministic budget was never reached (max 2.483/4.0). Those labellings were suboptimal AND load-dependent -- the wall clock is exactly the cap 39.5 added the deterministic one to escape. Cause: 38.14's t -> n adjacency makes the model much harder, and the 2s value dated from when solves took ~124 ms. Raised to 30s; 24/24 harbor and 36/36 maple now OPTIMAL, deterministic budget still in headroom (3.569/4.0). The verdict reverses. Deterministic, 12 seeds, scored canonically: harbor greedy 1323 (722h) 0.079 s/seed cpsat 1548 (908h) 1.623 maple greedy 1764 (777h) 0.063 s/seed cpsat 2256 (1213h) 1.327 cpsat loses on both, +225 and +492 fails at ~21x the seeding time, concentrated in hard fails. Time and quality have different causes. Removing t -> n from harbor takes cpsat 1.623 -> 0.193 s/seed (8.4x faster) but it is still +205 vs greedy (was +225) -- so the adjacency explains the time blow-up and ~9% of the quality gap; the regression is otherwise pre-existing. Squaring with 39.5: that section records cpsat returning 194/180/171/182 over four identical 10-seed aggregates before the determinism work. Its 10-fail harbor margin sits well inside a noise band that wide, and was measured with fdp's id()-ordered room_slots live. The seeder-level claim was never established rather than overturned. 39.5 annotated in place. Absolute totals are ~6x 39.5's because the objective has changed, so they are not comparable to that table; the within-measurement comparison is like-for-like and is what the verdict rests on. No default changes: assign_solver was already greedy for 37.7's independent reason. What changes is that "cpsat wins the seeder A/B" should no longer be cited as a reason to pursue it. The cap fix takes the suite from ~4.5 to ~10 min and the tests cannot opt out, since constructive_topology does not thread the solver limits through. Filed as homemaker-py-2xk. Closes homemaker-py-vjd. Lint at parity (46); tests 384 passed, 0 failed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MJ84Feep79Hhm3E4zZJmnB |
||
|---|---|---|
| .. | ||
| hooks | ||
| .gitignore | ||
| config.yaml | ||
| issues.jsonl | ||
| metadata.json | ||
| README.md | ||
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
Quick Start
Essential Commands
# 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:
# 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
- Quick Start Guide: Run
bd quickstart - Examples: github.com/steveyegge/beads/examples
Beads: Issue tracking that moves at the speed of thought ⚡