docs(accounts): propose group and context continuation policy

[tako0614]

Existing shared-account merge contracts leave multi-context accounts, later canonical-group merges, and a distinct operation after applied recovery without an adopted continuation policy. This docs-only follow-up proposes a versioned Accounts/Core group and context protocol for owner review, retaining original account IDs, Workspace/member custody, separate Organizations/wallets, historical references, and pending operation keys.

The proposal is unadopted and unimplemented. It distinguishes actual main dac30855915e49e5a4fb9782c489a023e7ed1f5a from the unmerged v1 candidate PR475 at 11d8acf5cae3d624dda6656d84bdcdccdc0585b6, using immutable source links. It preserves current safe refusals and same-operation retry/recovery obligations, requests explicit owner decisions on group-controller representation and Workspace continuity, and does not establish a final launch exclusion. The Japanese/English shared-account reference explains the current eligibility boundary and labels candidate context acceptance as pending.

Exactly five documentation files change. Runtime, schema, configuration and production defaults do not change. The earlier issuer/claims/client/session design remains the baseline. Actual review issuer, Financial/Hosted-intent/RP/Principal participant coverage, migration qualification, and staging/production activation remain separate requirements; no actual owner capability is qualified by this design.

Validation on exact head b2d2ba934158b851acb184f792dd445a228e9ef1:

• Exact command: bun run check, exit 0 / all 20 phases PASS / 463.686s, Bun 1.4.0+34cbb9a40 and Node v22.23.3 on a pinned nested PATH. Runner used umask 022 and a fresh environment allowlist (HOME, USER, SHELL, LANG, LC_ALL, LC_CTYPE, TERM, NO_COLOR, PATH, plus the two port variables). NODE_ENV/TAKOSUMI_ENVIRONMENT and credentials were absent; no dotenv files in execution roots. Browser ports were TAKOSUMI_E2E_PORT=43880 and TAKOSUMI_DOCS_BROWSER_PORT=43881.
• Main tests: 6367 pass / 0 fail / 5 existing skips, 126661 assertions across 598 files. Isolated workerd: 52 pass / 458 assertions; dashboard harness: 6 pass / 42 assertions; dashboard browser: 42 pass / 2 existing skips; docs browser: 3 pass. Dashboard/app docs/platform/auth-staging/bootstrap builds passed. No check was disabled or retried.
• Full log SHA256: b9be3cfcd20248a955f4ffb97d317028ff69acfa8d97fb9bbdc02ac5c966221d. Begin/end HEAD and all five frozen blobs matched; worktree clean. Native workerd/D1 and local OpenTofu checks exercise existing source, not the proposed v2 protocol. No provider operation, schema apply, credential/client registration, or stage/production publication occurred.

Focused documentation build and both JA/EN preview pages passed; relative links resolve and the internal proposal remains excluded from the public build. Independent read-only Core/normative review found no issues. These checks do not demonstrate proposed v2 runtime behavior.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-15T00:40:26.261415Z	b2d2ba9	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[tako0614]

品質・リリース担当へ、Accounts/Core の group/context continuation を扱う docs-only 設計提案の 新しい exact-head QA を依頼します。

対象 full head: b2d2ba934158b851acb184f792dd445a228e9ef1。

exact command: bun run check。固定 Bun 1.4.0+34cbb9a40 / Node v22.23.3、nested PATH 固定、umask 022、credentials/NODE_ENV/TAKOSUMI_ENVIRONMENT を含まない環境 allowlist、dotenv 無し、専用 browser ports 43880 / 43881 で exit 0 / 全20 phase PASS / 463.686s。

main 6367 pass / 0 fail / 既存5 skip / 126661 assertions / 598 files、isolated workerd 52 pass / 458 assertions、harness 6 pass / 42 assertions、dashboard browser 42 pass / 既存2 skip、docs browser 3 pass、dashboard/app-docs/platform/auth-staging/bootstrap builds PASS。開始・終了 HEAD / 全5文書 blob 一致、worktree clean。full log SHA256 b9be3cfcd20248a955f4ffb97d317028ff69acfa8d97fb9bbdc02ac5c966221d。チェック省略・再試行はありません。

変更は5文書のみ。v2 は 未採用・未実装の owner decision request です。actual main dac30855915e49e5a4fb9782c489a023e7ed1f5a と未 merge の v1 candidate 11d8acf5cae3d624dda6656d84bdcdccdc0585b6 を immutable permalink で区別し、現行安全拒否・same-op retry/recovery 義務を保持しています。group controller / Core continuity / full inventory / permission conflict / recovery ancestry / participant custody の提案をレビューし、既存 team/multiple contexts 等を暗黙の最終 scope 除外にしていないことも確認してください。JA/EN 公開 docs は actual-main eligibility と pending context acceptance を区別しています。

focused docs build / JA+EN preview / internal 非公開確認と、独立 read-only Core・規範レビューは PASS。既存 native fixture の全体 CI と提案 v2 の runtime proof は別です。実 issuer/approval/Financial/Hosted-intent/RP/Principal coverage、migration rehearsal、stage 資格は未構成・未確認で、この PR はそれらを qualified にしません。runtime/schema/config/key/client registration/deploy の変更・実行はありません。

他 PR の Approve を流用しません。正式判断はこの完全一致 SHA でお願いします。merge / rollout は依頼していません。

[tako0614]

品質・リリース判定: ✅ Approve（head b2d2ba9）

品質・リリース担当による exact-head レビュー結果です（docs-only）。

確認事項

• Head: PR head = b2d2ba934158b851acb184f792dd445a228e9ef1（指定 b2d2ba93 と一致、移動なし）。
• Base: main（stacked ではない）。merge-base = 現 main dac30855、mergeable=MERGEABLE / CLEAN。
• Local CI 記録: exact head の記録あり（PR コメント 2026-10-15 09:40 JST、Bun 1.4.0 / Node 22.23.3、bun run check 20/20 phases exit 0）。
• GHA: exact head で全 green（OSS quality 38661366582、dependency audit 38661366486、website artifact 38661366491）。
• main: dac30855 の quality / audit / website すべて success。
• 変更は docs 5 files（+275 / -0）のみ。コード・schema・workflow・依存の変更はない。

内容レビュー

• 共有アカウント（auth.takos.jp）、Workspace 単位、Control が membership / personal bootstrap / billing binding を所有する、という前提は確定設計と整合。email 一致や共有で権限・wallet を合算しない方針も維持。
• v2（group / context continuation）は「unadopted / unimplemented の owner decision request」と明記されており、現行 API への未実装手順の混入はない。日英 reference の内容は対応している。
• 新規 migration 番号の提案なし。staging / production 設定の変更なし。

Secret チェック

diff の credential 形状スキャンで該当なし。

マージ順・フォローアップ

• Compose private owner admission, identity, storage and metered runner #475 → docs(accounts): propose group and context continuation policy #476 の順を推奨。docs/internal/README.md が重複するが、merge-tree で conflict がないことを確認済み。
• 文中で Compose private owner admission, identity, storage and metered runner #475 を「pending / unmerged candidate」とし、11d8acf5 の permalink を参照している。Compose private owner admission, identity, storage and metered runner #475 の最終 head は 451e69bf（11d8 以降は test-only 変更で、参照行は同一）。Compose private owner admission, identity, storage and metered runner #475 の merge 後に表現を「merged」へ更新する follow-up docs PR を推奨（ブロッカーではない）。