docs: self-* スコープのユーザーガイド新設(Bolt 2 self-scopes — 260805-docs-impl-sync) - #2306
Merged
j5ik2o merged 2 commits intoAug 5, 2026
Merged
Conversation
The scope guide described ten scopes while the framework ships fifteen. Split the catalogue into the eleven general scopes and a dedicated section for the four self-development scopes, and add the previously undocumented installer-distribution scope. The new section explains what each self-* scope is for, why none of them is auto-detected, and why self-fix and self-refactor keep Comprehensive verification at Minimal depth. Depth, test strategy, and EXECUTE counts are transcribed from the compiled scope grid; the prose is derived from the scope files under packages/framework/core/scopes/. Extend the routing and test-strategy-default tables to all fifteen scopes, point the skills guide at the section from the scope-runner discussion, and cross-link it from the harness-engineering naming note.
The Japanese chapter promised a catalogue of ten scopes while the framework ships fifteen, and its English counterpart was already count-free. Match the English wording so the sentence no longer has to be resynchronised whenever a scope is added.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
j5ik2o
added a commit
that referenced
this pull request
Aug 6, 2026
…2302) * docs: reconcile scope and runner count words with the shipped catalog The framework ships fifteen scopes, not ten. Update the count words that sit next to an inline enumeration to the measured value and extend the enumeration with installer-distribution and the four self-* scopes; rewrite the prose count words that have no adjacent enumeration to a count-free form so they cannot go stale again. Drop the '37 runner descriptions' figure from the Codex CLI page for the same reason. * docs: cover all eight shipped sensor manifests and fix their source path The sensor reference exemplified only four of the eight shipped manifests and pointed at the generated dist/ tree as their home. List every manifest in the matches and timeout tables, add the missing event-registry-drift row to the harness-engineering inventory, and repoint the authoring and example paths at the canonical packages/framework/core/sensors/ source (the compile resolver walks the installed .claude/sensors/ tree, so that reference stays runtime-side). * docs: bring the harness roster and version facts up to date Add the Kimi Code and Pi Coding Agent badges, list pi/ in the harness and dist trees, add pi to the installer wizard roster, and enumerate all eight harnesses in the docs landing page. Correct the Kimi Code floor to 0.29.0 to match MIN_KIMI_VERSION, and resync the Japanese README version badge to 0.1.7. * docs: list the intent, space, codekb-path, and plugin verbs in the CLI reference The Quick Reference table omitted seven verbs that the utility CLI's own help output advertises. Transcribe them from that output. * docs: port the loop monitor and quality repair event section to Japanese The Japanese state-machine reference was missing the whole '### Loop monitor and quality repair' section, so five audit events had no Japanese counterpart. Port the heading, lead paragraph, and all five rows, keeping event names and emitter paths verbatim so the t48 forward check still matches. Scope declaration: the authorized change was the two events AUTO_DECISION_REVIEWED and INTENT_COMPLETION_TRANSACTION_COMMITTED. Porting only those two was not realizable because the containing section was absent entirely; election E-DIS-CG1 (choice 1, 2-0) authorized widening this to the whole section. * docs: correct the scope count and roster in the architecture reference Same defect as the count words already fixed in the skills and scopes chapters: the architecture summary claimed ten named scopes next to an inline enumeration. Update to the measured fifteen and extend the enumeration with installer-distribution and the four self-* scopes. * docs: self-* スコープのユーザーガイド新設(Bolt 2 self-scopes — 260805-docs-impl-sync) (#2306) * docs: document the self-* scopes and the installer-distribution scope The scope guide described ten scopes while the framework ships fifteen. Split the catalogue into the eleven general scopes and a dedicated section for the four self-development scopes, and add the previously undocumented installer-distribution scope. The new section explains what each self-* scope is for, why none of them is auto-detected, and why self-fix and self-refactor keep Comprehensive verification at Minimal depth. Depth, test strategy, and EXECUTE counts are transcribed from the compiled scope grid; the prose is derived from the scope files under packages/framework/core/scopes/. Extend the routing and test-strategy-default tables to all fifteen scopes, point the skills guide at the section from the scope-runner discussion, and cross-link it from the harness-engineering naming note. * docs: drop the stale scope count from the Japanese scopes chapter The Japanese chapter promised a catalogue of ten scopes while the framework ships fifteen, and its English counterpart was already count-free. Match the English wording so the sentence no longer has to be resynchronised whenever a scope is added. * docs: 未記載ツール群の文書補完と Intent autonomy 新章(Bolt 3 tool-docs — 260805-docs-impl-sync) (#2310) * docs: document the TLA+ authoring CLI and evidence store * docs: document the plugin import-closure guard * docs: add the Intent autonomy, review, and completion reference chapter * docs: document the advisory choice acceptance paths * docs: correct the packaged harness face count and roster for the pi face * docs: use a stage runner in the Codex stage-runner example The sentence introduces stage runners, but one of its two examples was $amadeus-fix — a scope runner. Swap it for $amadeus-code-generation so both examples match the runner kind the sentence describes. Addresses coderabbit review on #2302. * docs: 凍結注記・ファイル目録現況化・live-e2e 対訳と索引(Bolt 4 freeze-and-parity — 260805-docs-impl-sync) (#2314) * docs: mark the upstream sync report as a frozen snapshot The report is a point-in-time investigation pinned to the revisions in its Compared revisions table. Readers reached it without any signal that it is not maintained, so state the freeze, point at the pinned revisions, and say it does not reflect current state. * docs: refresh the generated file inventory against the current tree The inventory was pinned to commit 9b77786 (2026-07) and had drifted: the hook, sensor and tools/data listings were short, otel/ and vendor/ were absent, .agents/ omitted rules/, the tools count was stale, and two stage outputs used retired artifact names (test-results rather than build-test-results and load-test-results). Re-measure from bun run dist and the produces: frontmatter, and index the page from docs/README. * docs: add the Japanese live harness end-to-end runbook The runbook was English-only while every other harness-engineering page ships a translation. Add the Japanese rendering and the language switch links the docs gate requires once the pair exists. The generated matrix block stays in the English page alone, since project-matrix.ts writes only that file and a duplicated block would drift silently. * docs: index the file inventory and live e2e runbook from the docs map Both pages were unreachable from the documentation map. Add one link line each, keeping the additions purely additive so parallel edits to this file do not conflict.
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.
概要
intent
260805-docs-impl-syncの Bolt 2 —self-*4 スコープのユーザー向け解説の新設(FR-3 = 乖離目録 C-1 / F-1)。裁定 Q2=B(一般と自己開発の分離)+ FD-Q2=A(05 章内の専用 H2 節)。Bolt 1(#2302)に積んだ stacked PR(base =bolt/docs-sync-divergence-fixes)。#2302 のスカッシュ着地後に base を main へ付け替え、rebase --ontoで transplant する。変更
docs/guide/05-scopes-and-depth.{md,ja.md}— 「The 10 Scopes」→「The 11 General Scopes」(欠落していたinstaller-distributionを追補)+ 専用 H2 節「Self-development scopes (self-*)」新設(4 スコープの表・auto-detect されない性質・検証は depth に縮退しない性質・選び方 H3)。ルーティング表と test-strategy 既定表を 15 スコープへ拡張docs/guide/17-skills.{md,ja.md}— scope-runner 節へ self-* の到達経路(/amadeus --scope self-*)1 文+新節リンクdocs/harness-engineering/04-scopes.{md,ja.md}— self-* 命名注記から新節への相互参照、JA :9 の stale 件数語「10スコープ」を EN と対の count-free へ実測根拠
ls packages/framework/core/scopes/bun dist/claude/.claude/tools/amadeus-utility.ts scope-table(worktree 内bun run dist後の実出力。self-document 9/32、self-feature 14/32、self-fix 7/32、self-refactor 8/32 — 各スコープファイルの stage 記述と相互検算一致)検証(ローカルを正 — docs-only、#2278 参照)
Refs: #2302(base)、intent record
amadeus/spaces/default/intents/260805-docs-impl-sync/Note
Low Risk
Documentation-only changes with no runtime, auth, or build logic touched; risk is limited to doc accuracy and EN/JA parity.
Overview
User guide (
05-scopes-and-depthEN/JA) reframes the catalog as 11 general scopes plus fourself-*scopes (15 total). It adds the missinginstaller-distributionsubsection, a new Self-development scopes (self-*) section (tables, explicit-only selection viakeywords: [], Comprehensive test strategy despite Minimal depth for fix/refactor, and when to pick each scope), and extends the routing table, test-strategy defaults, and “choosing the right scope” rows accordingly.Skills guide (
17-skillsEN/JA) notes thatself-*scopes are reached only via/amadeus --scope self-*(no dedicated runners), with a link to the new section.Harness engineering (
04-scopesEN/JA) drops stale “10 scopes” wording, points the full catalog at the user guide, and linksself-*naming to the same section.Reviewed by Cursor Bugbot for commit 261b50b. Configure here.