The migration-test harness (scripts/migration-test/) already builds a
BUG->TASK dependency fixture (create_dataset in lib/features.sh: `dep add
"$bug_id" "$task_id"`, i.e. bug depends on task, task is the blocker) and
migrates it in place with the candidate binary, but only verified fidelity
via bd list/show JSON. It never exercised bd's blocker-aware query paths on
the migrated DB, which is exactly the surface of the historical `bd close`
Dolt errno 1105 failure on a stale post-migration dependency schema
(verified manually for the 1.0.5 release in mybd-kdxj).
Add check_blocker_paths() in lib/snapshot.sh, run against the migrated DB
after check_fidelity in all three harness outcomes (direct upgrade, recipe
fallback, stepping-stone) plus the --self-test path:
- bd blocked lists the dependent (bug) while the blocker (task) is open
- bd ready excludes the dependent but includes the open blocker
- bd close on the blocker succeeds post-migration (the errno 1105 path)
- bd ready then lists the dependent (unblock/is_blocked recompute)
Violations fold into the existing violation count and flip AUTO/MANUAL
results to BLOCKED so a regression fails the harness loudly, matching the
existing report.sh exit-code convention. Skips gracefully when the source
version's dataset has no dependency.
cross-version-smoke.yml's parallel gate (scripts/upgrade-smoke-test.sh)
already added equivalent Scenario 6 blocker-path assertions in #4238; no
change needed there.
Verified: `--self-test` (candidate -> candidate, no downloads) and a real
`v0.63.3 -> candidate` direct upgrade both pass with the new BLOCKER-CHECK
line green.
Agent-Signature: claude-opus-4-8-high on behalf of matt wilkie
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Multi-hop upgrade paths through old releases are inherently broken
because intermediate binaries have bugs that cannot be patched
retroactively. Users should upgrade directly to the latest release.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
BEADS_TEST_MODE=1 disables Dolt server auto-start and forces port 1,
which makes every bd command fail for server-era versions (v0.50-v0.62).
Change default to 0 since the harness runs in isolated temp-dir
workspaces. Also make epic creation non-fatal with task fallback.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* wip: add migration test harness for cross-era upgrade fidelity
Rich dataset generator, field-level fidelity checker, and migration
recipes for SQLite/Dolt-server/embedded-Dolt eras. Addresses GH#2938
upgrade pain by testing and documenting working upgrade paths.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: snapshot JSON format handling and self-test mode
- show --json returns array, not object — use jq array concatenation
- Field is issue_type not type in bd JSON output
- Normalize empty comment_count to 0 (show vs list field differences)
- Add --self-test flag for harness validation without old binaries
- Fix local variable outside function in self-test block
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* ci: re-trigger Kilo Code Review
* address review: timeouts, env var docs, quoting
- Add BD_OP_TIMEOUT (30s) for bd operations via timeout(1)
- Add DOWNLOAD_TIMEOUT (60s) for curl binary downloads
- Document all environment variables in run.sh header
- Convert init_flags from word-split string to proper bash array
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: fall back to source build when release binary has missing shared libs
Downloaded release binaries dynamically link ICU (libicui18n.so.74),
which isn't available on all systems. Now download_binary verifies the
binary actually runs, and falls back to building from source with
gms_pure_go tag when it doesn't. Also applies gms_pure_go to
build_candidate for consistency.
Ref: gastownhall/beads#3065
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>