Repository navigation
docs: Update README / CONTRIBUTING links to basou.dev - #1
Merged
Merged
Conversation
The operator-facing quickstart now lives on basou.dev (the site content is bilingual and tracks the v0.3 spec). This commit points README / CONTRIBUTING at the canonical URLs rather than the docs/quickstart.md redirect stub. - README "Quickstart" reference, npm publish milestone reference, and the Project Structure inline comment now point at basou.dev/quickstart/ (or basou.dev/installation/ for the install path lookup). - CONTRIBUTING's bug-report sanity-check link and the dev-setup quickstart link follow the same pattern. - README "Links" section gains a Documentation row so readers have a direct entry point into basou.dev/getting-started/ alongside Website / GitHub / npm. docs/quickstart.md stays as a redirect stub so existing external links continue to resolve. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
takashi-matsuyama
added a commit
that referenced
this pull request
Jul 1, 2026
…view) Applies the adversarial review of the repository_url removal. - B3 (spec-deviation, operator's call): README promises the 0.x CLI surface is frozen (commands and flags stable). Removing --repo-url outright broke that. Keep --repo-url accepted as a deprecated no-op through 0.x -- it writes nothing (the field is gone) and warns that it is ignored -- and remove the flag at 1.0. The schema field removal + migration stay (formats are only committed at 1.0, and the change is forward-safe). - Finding #1 (doc drift): docs/spec/schemas.md still listed project.repository_url in the manifest example; removed it. Deferred to backlog (operator's call): strip-on-every-write vs a dedicated migration (B1), a notice when a legacy field is dropped (B2), an SDK-facing deprecation note (B4). Tests: --repo-url is accepted, writes no repository_url, and warns. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
takashi-matsuyama
added a commit
that referenced
this pull request
Jul 1, 2026
…154) * feat(schema): remove project.repository_url (M4 pre-freeze cleanup) The manifest field was a write-once copy of git's remote.origin.url that no code read and that drifted silently on an org move / rename -- a second source of truth for a fact git already owns. The manifest holds only declarative intent; the remote is an observed git fact, derived live where needed (the portfolio view already does this). Settles the A side of decision_01KWDX4ZE8. - Removed `repository_url` from ProjectSchema; regenerated manifest JSON Schema. - createManifest no longer accepts/emits it; `basou init` drops the `--repo-url` flag and the tryRemoteUrl capture. - ProjectSchema stays looseObject (forward-compat), so a legacy value survives parse as an unknown key -- writeManifest strips only that one field so any manifest rewrite self-heals, while other unknown keys stay preserved. Tests: createManifest never emits it; writeManifest strips a legacy value; init never writes it even with a git remote set; the schema still accepts (and preserves) a legacy value on read. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(init): keep --repo-url as a deprecated no-op; update spec doc (review) Applies the adversarial review of the repository_url removal. - B3 (spec-deviation, operator's call): README promises the 0.x CLI surface is frozen (commands and flags stable). Removing --repo-url outright broke that. Keep --repo-url accepted as a deprecated no-op through 0.x -- it writes nothing (the field is gone) and warns that it is ignored -- and remove the flag at 1.0. The schema field removal + migration stay (formats are only committed at 1.0, and the change is forward-safe). - Finding #1 (doc drift): docs/spec/schemas.md still listed project.repository_url in the manifest example; removed it. Deferred to backlog (operator's call): strip-on-every-write vs a dedicated migration (B1), a notice when a legacy field is dropped (B2), an SDK-facing deprecation note (B4). Tests: --repo-url is accepted, writes no repository_url, and warns. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <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
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
docs/quickstart.mdstub references inREADME.mdandCONTRIBUTING.mdwith the canonicalbasou.dev/quickstart/andbasou.dev/installation/URLs.basou.dev/getting-started/.docs/quickstart.mditself stays as a redirect stub so existing external references continue to resolve.Implements the link-update step from the M-3 §4.2 migration plan now that basou-site is live with bilingual Phase 0/1 content and Cloudflare Web Analytics is enabled.
Test plan
pnpm typecheck/pnpm test/pnpm lintpass on CI (= quality.yml).docs/quickstart.mdstub still loads from the README "Project Structure" line as a sanity reference.