Skip to content

docs: 未記載ツール群の文書補完と Intent autonomy 新章(Bolt 3 tool-docs — 260805-docs-impl-sync) - #2310

Merged
j5ik2o merged 5 commits into
bolt/docs-sync-divergence-fixesfrom
bolt/docs-sync-tool-docs
Aug 5, 2026
Merged

docs: 未記載ツール群の文書補完と Intent autonomy 新章(Bolt 3 tool-docs — 260805-docs-impl-sync)#2310
j5ik2o merged 5 commits into
bolt/docs-sync-divergence-fixesfrom
bolt/docs-sync-tool-docs

Conversation

@j5ik2o

@j5ik2o j5ik2o commented Aug 5, 2026

Copy link
Copy Markdown
Member

概要

intent 260805-docs-impl-sync の Bolt 3 — 実装済みだが docs 未記載のツール群の文書補完(FR-5 の F-2〜F-7、FD-Q1=B 裁定 = 既存章への節追加を既定とし Intent autonomy 系のみ新章)。Bolt 1(#2302)に積んだ stacked PR#2302 着地後に base を main へ付け替え transplant する。

変更(12 ファイル +712 行 + 畳み込み 1 件、全 EN/JA 対)

  • F-2docs/reference/22-formal-model-supply.{md,ja.md}: TLA+ authoring CLI(tla-authoring.ts)の契約と subcommand 群、evidence store(tla-evidence.ts — 実読の結果 CLI ではなく library と確定し、そのとおり記述)
  • F-3docs/guide/19-plugins.{md,ja.md} + docs/reference/11-contributing.{md,ja.md}: plugin import-closure guard(scripts/import-closure-guard.ts)を plugin 作者視点と貢献者視点で書き分け
  • F-4/F-5/F-6新章 docs/reference/24-intent-autonomy.{md,ja.md}: autonomy モード/グラント、decide-question(AUTO_DECIDED)、review surface、Intent completion seal、harness registry。章番号 24 は起草時とコミット直前の 2 回git fetch 後の git ls-tree origin/main docs/reference/ 実測で空きを確認(cid:code-generation:shared-ledger-insert-collision 追補準拠 — マージ直前にも再確認する)
  • F-7docs/reference/12-state-machine.{md,ja.md}: advisory 選択の受理経路(record verb・HUMAN_TURN 束縛・冪等受理・correct-misattributed)の H4 追加
  • 畳み込み(同根、Q1=B 執行): 19-plugins の「Seven packaged faces」→ 実測 8(pi 追加)

検証(ローカルを正 — docs-only、#2278 参照)

検証 結果
t174(unit) exit 0 — 5 pass
t48 + t52 + t287 + t291 + t-pi-docs(integration) exit 0 — 31 pass / 0 fail(コミット後再実行も 0)
受け入れ grep: 7 識別子の EN/JA 両面 ≥1 hit + 解説実体 全成立
H2 parity(22 / 19 / 11 / 12 / 新 24 章) 全一致(24 章 5/5)
git status docs/ のみ。並行 Bolt 予約ファイル(05/17/04-scopes)不変

内容はすべて対象実装の実読からの転記(NFR-3)。ブリーフとの相違 2 件(tla-evidence の CLI 性、行数)は実読を正として記述し申告済み。

Refs: #2302(base)、intent record amadeus/spaces/default/intents/260805-docs-impl-sync/


Note

Low Risk
Documentation-only changes with no runtime or auth logic modified; risk is limited to doc drift or incorrect CLI paths if implementations change later.

Overview
Documentation-only sync for tools that already ship in the framework: twelve EN/JA files gain or extend reference material, and the docs index links the new Intent autonomy chapter.

New chapter docs/reference/24-intent-autonomy.{md,ja.md} documents Intent-scoped autonomy (none / semi / full), grant confirmation via amadeus-bolt, decide-question / AUTO_DECIDED, the append-only auto-decision review surface, the completion seal from amadeus-intent-completion.ts, and amadeus-harness-registry.ts as the single harness capability table.

Formal model supply (22-formal-model-supply) now describes the tla-authoring CLI (identity, bundles, applicability, hold / advisory hold) and tla-evidence.ts as a library writer for specs/tla-evidence, not a standalone CLI.

Plugins (19-plugins + 11-contributing) document the import-closure guard (scripts/import-closure-guard.tsassertPluginImportClosure at package time), failure message shapes, and tests t440t443. The same pass updates packaged harness coverage from seven to eight faces (pi added to auto-compose, folder-drop-auto, and --project-root notes).

State machine (12-state-machine) adds a subsection on advisory choice acceptance: run-now / defer-with-risk, prompt vs record verb, HUMAN_TURN binding, idempotency, and correct-misattributed.

Index: docs/README.{md,ja.md} link Intent autonomy, review, and completion at reference/24-intent-autonomy.

Reviewed by Cursor Bugbot for commit f4d99c2. Configure here.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)
  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d95b9a8e-460e-46fa-8b70-f0e623585d70

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@j5ik2o
j5ik2o merged commit ad7c9bc into bolt/docs-sync-divergence-fixes Aug 5, 2026
16 checks passed
@j5ik2o
j5ik2o deleted the bolt/docs-sync-tool-docs branch August 5, 2026 16:15
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant