docs: clean-slate v1 — drop migration prose, milestone framing, 0.x caveats#90
Merged
Conversation
The site reads as if v1 is the only reality — there is no installed base on a prior layout to migrate from. Delete the migration guide and its inbound links from configuration.md, indexing-a-repo.md, and storage-backend.md. Update the llms-txt customSet description so it no longer advertises a migration guide.
…flip LadybugDB is the default; the single-file DuckDB layout is the opt-in fallback for environments where the @ladybugdb/core binding cannot load. Drop "M7 default-flip", "legacy default", and "what's new" prose across storage-backend, overview, determinism, monorepo-map, install, quick-start, what-is-opencodehub, configuration, indexing-a-repo, and troubleshooting. ADR 0013 is now described as recording a decision, not as a flip event.
… how it evolved Site prose now describes the current shape of the system without pinning behavior to milestones. ADR cross-references are reframed as "records this decision" rather than "this milestone delivered X". Trims the canned-prompts page so it explains why playbooks live as skills instead of narrating a removal event.
Conventional Commits is a reference; the rule list does not need a "while we're on 0.x" preamble. feat! and BREAKING CHANGE: footer both bump the major version — that is the rule, stated forward-looking.
Closed
theagenticguy
added a commit
that referenced
this pull request
May 10, 2026
…aveats (#90) ## Summary The docs site now reads as if v1 is the only reality. There's no installed-base on a prior version and nothing to "migrate from" — every install starts on the LadybugDB default with the DuckDB single-file layout as a fallback when the binding cannot load. Per user directive: "assume no one but me has used this so far. clean slate based on current head of repo." ## Changes (4 commits) 1. **`04db651` drop `migrating-from-duckdb` guide + cross-refs** — `git rm packages/docs/src/content/docs/guides/migrating-from-duckdb.md` plus references in `configuration.md`, `indexing-a-repo.md`, `storage-backend.md`, and the llms-txt customSet description in `astro.config.mjs`. 2. **`7c96429` reframe storage as default+fallback** — `storage-backend.md`, `overview.md`, `determinism.md`, `monorepo-map.md`, `start-here/install.md`, `start-here/quick-start.md`, `start-here/what-is-opencodehub.md`, `reference/configuration.md`, `guides/indexing-a-repo.md`, `guides/troubleshooting.md`. "M7 default-flip" / "legacy default" / "since v1.0" prose → "default + opt-in fallback when `@ladybugdb/core` cannot load." 3. **`8bec91f` drop M3-M7 milestone framing** — `architecture/cross-repo-federation.md`, `architecture/lessons.md`, `architecture/adrs.md`, `mcp/overview.md`, `mcp/prompts.md`. Reframed ADR cross-references as "records this decision" rather than "M7 delivered X"; rewrote prompts page as design rationale rather than removal narration. 4. **`d0db801` drop 0.x BREAKING-change caveats from contributing** — `contributing/release-process.md`, `contributing/commit-conventions.md`. "While OCH sits on 0.x.y..." → forward-looking rule: `feat!` / `BREAKING CHANGE:` bumps major. ## Validation - `pnpm -F @opencodehub/docs build` — clean, 64 → 63 pages (one deletion), all internal links valid - `bash scripts/check-banned-strings.sh` — PASS - `rg 'AC-[A-Z]-[0-9]|T-M[0-9]+-[0-9]+|W-[A-Z]-[0-9]+|S-[A-Z]-[0-9]+|E-[A-Z]-[0-9]+|CL-[A-Z]+'` packages/docs/src/ — zero hits - `rg 'migrat\|previously\|formerly\|legacy default\|0\.x'` packages/docs/src/ — zero prose hits (pnpm 10.x toolchain references remain — those describe pnpm's major version line, not OCH's release line) ## Test plan - [ ] CI green - [ ] After merge, Pages workflow re-deploys and the site reads forward-only
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.
Summary
The docs site now reads as if v1 is the only reality. There's no installed-base on a prior version and nothing to "migrate from" — every install starts on the LadybugDB default with the DuckDB single-file layout as a fallback when the binding cannot load. Per user directive: "assume no one but me has used this so far. clean slate based on current head of repo."
Changes (4 commits)
40b6886dropmigrating-from-duckdbguide + cross-refs —git rm packages/docs/src/content/docs/guides/migrating-from-duckdb.mdplus references inconfiguration.md,indexing-a-repo.md,storage-backend.md, and the llms-txt customSet description inastro.config.mjs.e05cd50reframe storage as default+fallback —storage-backend.md,overview.md,determinism.md,monorepo-map.md,start-here/install.md,start-here/quick-start.md,start-here/what-is-opencodehub.md,reference/configuration.md,guides/indexing-a-repo.md,guides/troubleshooting.md. "M7 default-flip" / "legacy default" / "since v1.0" prose → "default + opt-in fallback when@ladybugdb/corecannot load."63a6c0bdrop M3-M7 milestone framing —architecture/cross-repo-federation.md,architecture/lessons.md,architecture/adrs.md,mcp/overview.md,mcp/prompts.md. Reframed ADR cross-references as "records this decision" rather than "M7 delivered X"; rewrote prompts page as design rationale rather than removal narration.cd388bbdrop 0.x BREAKING-change caveats from contributing —contributing/release-process.md,contributing/commit-conventions.md. "While OCH sits on 0.x.y..." → forward-looking rule:feat!/BREAKING CHANGE:bumps major.Validation
pnpm -F @opencodehub/docs build— clean, 64 → 63 pages (one deletion), all internal links validbash scripts/check-banned-strings.sh— PASSrg 'AC-[A-Z]-[0-9]|T-M[0-9]+-[0-9]+|W-[A-Z]-[0-9]+|S-[A-Z]-[0-9]+|E-[A-Z]-[0-9]+|CL-[A-Z]+'packages/docs/src/ — zero hitsrg 'migrat\|previously\|formerly\|legacy default\|0\.x'packages/docs/src/ — zero prose hits (pnpm 10.x toolchain references remain — those describe pnpm's major version line, not OCH's release line)Test plan