docs(post-v0.4): refresh stale .worktree-isolation.yaml / DB plugin references#19
Merged
Merged
Conversation
…eferences
Several user-visible and source-comment strings still read like v0.3 even
after the v0.4 rename:
- internal/backend/detect.go pkg doc + error message
- internal/envwriter/envwriter.go pkg doc + .env.local footer
(rendered into every worktree's
.env.local, so every operator sees it)
- internal/gitwt/gitwt.go DetectBase doc comment
- README.md Roadmap v0.4 row + Status section
- tests/integration/e2e_mysql_test.go fixture bumped to v0.4 canonical
(schema_version: 2 / engines: /
port_ranges: / initial_resources: /
role: engine-provider /
.bough.yaml + .bough-ports.json /
registry key mysql.main)
The v0.3 → v0.4 migrateLegacy() path stays covered by the existing
config_test.go unit tests (TestLoad_validExample + TestLoad_migrateLegacy_v03);
the e2e test now exercises the canonical v0.4 wiring end-to-end so a
future schema bump cannot regress it silently.
Intentional v0.3 mentions (CHANGELOG history, MIGRATION doc, fallback
impl in helpers.go / config.go / registry.go, deprecation messages, test
fixtures under testdata/) are left untouched — they describe the v0.3
fallback the v0.4.x line still honours.
go build ./... + go vet ./... + go test ./internal/... ./conformance/...
+ golangci-lint clean locally.
ikeikeikeike
added a commit
that referenced
this pull request
Jun 19, 2026
Bundles the work shipped on main since v0.4.0: - cobra help text refresh (#18) - .env.local footer + backend error + doc-comment sweep (#19) - README/MIGRATION + plugins/db/CONTRACT.md drop + nix-default clarification (#20) - smoketool extraction + lifecycle.go/create.go phase split (bc05a88) - CI conformance matrix path fix (3f133c0) No behaviour change; all docs / strings / refactor.
ikeikeikeike
added a commit
that referenced
this pull request
Jul 4, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sweep follow-up to #17 + #18: user-visible / source-comment strings that
still read like v0.3.
Touched:
(rendered into every worktree's `.env.local`, so every operator sees it)
canonical (`schema_version: 2` / `engines:` / `port_ranges:` /
`initial_resources:` / `role: engine-provider` / `.bough.yaml` /
`.bough-ports.json` / registry key `mysql.main`)
The v0.3 → v0.4 migrateLegacy() path stays covered by the existing
config_test.go unit tests (TestLoad_validExample + TestLoad_migrateLegacy_v03);
the e2e test now exercises the canonical v0.4 wiring end-to-end so a
future schema bump cannot regress it silently.
What was deliberately left alone
`internal/cli/helpers.go`, `internal/registry/`
`TestLoad_validExample` feeds into the migration path)
Python helper) in source comments
Test plan