225e673ae3
run_staged_search.py reported MISMATCH on its BASELINE arm -- the LEAFSHARE=0/MULTIUSE=0 control every A/B compares against. Two facts combined: driver.search_staged had no collapse_insearch parameter at all, so every inner search() call inherited search()'s True default unconditionally; and no example patterns.config sets the key, so the final _native_score rescore got False from a bare load_config. Search optimised one objective, the rescore graded another. The 7ua fix pinned the key inside a fitness.load_config monkeypatch, but that patch was installed only `if leaf_share or multi_use` -- so it fixed every arm except the control. Fixed in the right place: search_staged now HAS the parameter (default True, byte-identical to the inherited default), threaded into all three internal search() calls. The harness chooses the arm explicitly (COLLAPSE, default 1), passes it to the search, and passes the SAME value to _native_score, which overrides the key rather than hoping the config carries it. The rescore mirrors the search by construction. Verified on programme-house, budget 150: baseline MISMATCH 1.56663e-08 vs 1.51708e-08 -> OK COLLAPSE=0 (knob did not exist) -> OK 1.66216e-08 LEAFSHARE=1 / MULTIUSE=1 -> OK COLLAPSE=0 scoring differently confirms the knob is not a no-op, and the default arm's search result is unchanged, so no prior staged number moves. Audited the other three search_staged callers: run_and_capture_91f.py already pins collapse_insearch: True; run_island_ab.py never re-scores; probe_harbor_floor.py did NOT pin it and had the same bug -- now fixed, and that is the harness which produced every 13.x floor number. The recorded mitigating factor -- only the continuous score moved, the fail count matched, and the run_*_ab.sh greps read only the count -- is true and is exactly what made it dangerous: a harness that reports MISMATCH on its own control, invisibly to the metric of record, trains everyone to ignore the warning. Closes homemaker-py-4ok. Lint at parity (46); tests 381 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 ⚡