Repository navigation
Sweep v0.x-epoch framing and self-contradictions out of the docs - #50
Merged
Merged
Conversation
The hand-maintained catalog had drifted from the shipped CLI: it omitted import, refresh, view, and stats, and listed commands that no longer exist (session new, config). Replace the version-annotated flag-level catalog with a top-level command-group map plus a pointer to the generated, always-current reference at basou.dev/commands/reference (and `basou <command> --help`), which is regenerated from the CLI on every release and cannot re-drift. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…i-root scope The spec corpus was written in v0.1/v0.2 epoch framing that has since gone stale. Bring it to current reality: - overview: claude-code is no longer the only adapter (codex import shipped), and import is no longer JSON-only; the run adapter wraps claude-code as a child process while import adapters read native logs read-only. - workspace: reconcile "one repository = one workspace" with the shipped multi-root capture (repeatable --project / manifest.import.source_roots, see terminal-and-import section 14.3); fix the stale `basou task create` example to `basou task new`; drop the version tag from the index-lock candidate (it remains unimplemented, distinct from the task/session locks). - Drop version-coupled phrasing (v0.1/v0.2/v0.3 framing, "v0.4+" futures) across approval, generated-markdown, schemas, terminal-and-import, and the docs index, preferring version-independent wording to prevent re-staling. The "Added in v0.2" event-catalog annotations are kept as historical provenance. Schema versions (0.1.0) are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- CONTRIBUTING: replace "early pre-OSS / v0.3.x line" with version-independent wording (scoped @basou/* packages published, APIs still stabilizing) and drop the v0.1/v0.3 framing from the pathless-error note. - README: de-version the package table and the --version examples; the version badge and status line remain the single intentional current-version surface. - release-checklist: de-version the "current 0.3.1 line" lead-in and backfill the published-releases table with 0.4.0 through 0.7.0 (all on npm). The 0.3.1 and 0.6.0 captured dry-run blocks stay as dated evidence. - bug_report: drop the stale 0.3.1 version example and point the sanity-check reference at the canonical basou.dev URL (the local quickstart is now a redirect stub without that anchor). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The Test step comment hardcoded a "v0.3.1 baseline is 1015 tests" count that has long since drifted from the suite. Replace it with a version- and count-independent note so it does not re-stale on every test addition. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
What
Repo-wide docs sweep bringing v0.x-epoch phrasing and self-contradictions in
line with the published 0.7.0 reality. This finishes the Tiered work that was
intentionally deferred during the 0.7.0 docs refresh (#49).
Scope (Hybrid)
The docs/spec corpus was pervasively written in v0.1/v0.2 epoch framing. This PR:
surface in overview; the multi-root capture vs. "one repository = one
workspace" contradiction in workspace; a non-existent
basou task createexample; and the CLI catalog (which omitted import/refresh/view/stats and
listed the non-existent
session new/config)."v0.4+") to version-independent wording so the docs do not re-stale.
and leaves schema versions (0.1.0) and the dated dry-run evidence blocks
untouched.
Commits
docs(spec): refresh the CLI command catalog-> a pointer to the generated,always-current reference (basou.dev/commands/reference) plus a top-level
command-group map, instead of a hand catalog that re-drifts.
docs(spec): de-version the spec and correct adapter, import, and multi-root scope.docs: align contributor and release docs with the published line(CONTRIBUTING, README package table + --version examples, release-checklist
published-releases backfill 0.4.0 through 0.7.0, bug_report).
ci(quality): drop the stale hardcoded test-count comment.Notes
single current-version surface; only the package table and
--versionexamples were de-versioned.
though 0.4.0 is published on npm.