docs: reconcile canonical runtime authority with protected develop

[seonghobae]

Buyer and maintainer impact

Protected develop ships both the standalone planner and a Node/Hono Cloud/SaaS runtime, while canonical guidance had retained static-only and obsolete integration references. This lane reconciles buyer/maintainer authority with protected runtime truth without promoting active-PR behavior to shipped status.

Exact current identity

• protected live base: develop@2c328875e00e86537df3e965170be80532571cad;
• exact contributor head: abc9639ffd7a6bd835a0f8206854185722d60965;
• branch: docs/reconcile-shipped-runtime-authority-20260815;
• Ready and mechanically mergeable at the latest fresh refetch;
• no qualifying independent current-head approval exists.

Any head/base movement invalidates revision-sensitive evidence until the exact revisions, actual checkout attestations, reviews, checks, and live-base identity are freshly revalidated. This body is traceability, not merge authority.

Reconciled authority

• preserves standalone static-host compatibility while recognizing the protected Node/Hono Cloud/SaaS runtime and SQLite persistence as shipped;
• keeps PostgreSQL and other active-PR capabilities labeled as planned/active work rather than protected truth;
• replaces the historical fixed merge-map with live protected-head/base/head ancestry and current-evidence guidance;
• records descriptive multiword snake_case/3NF expectations for new owned database objects;
• aligns repository-native versus organization-required workflow ownership;
• points environment-variable guidance at docs/deploy.md rather than the removed README table; and
• keeps AGENTS.md, CLAUDE.md, ARCHITECTURE.md, and README.md consistent on current runtime and merge authority.

Review repairs and executable contract

Current source now satisfies the registered tests/unit/documentation-authority.test.mjs contract:

• CLAUDE.md no longer points to the removed README Merge order section and instead requires fresh protected-head/PR ancestry evidence;
• CLAUDE.md no longer points environment variables at the removed README table and now directs maintainers to docs/deploy.md;
• README cannot silently restore an obsolete fixed merge-order heading at another Markdown level; and
• the deployment guide remains the asserted environment-variable destination.

The valid environment-reference review thread was resolved only after commit abc9639ffd7a6bd835a0f8206854185722d60965 landed and exact source was refetched. Remaining unresolved inline threads are informational observations, not known unaddressed defects, and are not being mass-resolved.

Current evidence state

The current head move triggered fresh repository workflows. At the latest refetch, Server Tests, Fuzz, Security Scan, SAST Semgrep, Dependency Review, and OSV Scanner are queued and therefore non-passing. Historical predecessor-head successes are not transferred to this revision. Current formal submissions are COMMENTED/model evidence only; there is no qualifying independent current-head/last-push approval.

Merge gate

Do not merge or enable auto-merge until the unchanged exact head remains reconciled to freshly resolved protected develop, every applicable repository and organization CI/browser/coverage/docstring/CodeQL/SAST/security/dependency/supply-chain/package/provenance/required-workflow gate is substantively terminal-passing on the actual current head under live rulesets, valid unresolved findings are zero, and a qualifying independent current-head/last-push approval genuinely exists. Pending, queued, skipped-required, cancelled, absent, neutral-required, failed, stale, predecessor, synthetic-only, status-only, author-only, or model-only evidence is non-passing.

[coderabbitai]

📝 Walkthrough

Walkthrough

Standalone 및 Cloud/SaaS 프로필을 기준으로 저장소 문서를 개편했습니다. 런타임·데이터·보안·배포 경계와 검증·리뷰·릴리스 규칙을 추가했습니다. 문서 권위 검증 테스트도 추가했습니다.

Changes

저장소 운영 기준

Layer / File(s)	Summary
제품 프로필 및 런타임 계약 AGENTS.md, ARCHITECTURE.md, README.md	Standalone planner와 Cloud/SaaS overlay의 범위, 실행 모델, Hono 서버 구성, tasks, renderAll(), app.js 및 전역 브리지 계약을 정리했습니다.
Persistence, 보안 및 배포 경계 AGENTS.md, ARCHITECTURE.md, README.md	localStorage, File System Access API, SQLite, 테넌트 권한, 외부 어댑터 검증, 보안 통제와 배포 표면을 문서화했습니다.
검증 및 릴리스 게이트 AGENTS.md, ARCHITECTURE.md, README.md, package.json, tests/unit/documentation-authority.test.mjs	단위·API·coverage·E2E·Cloud E2E·fuzz 검증과 exact-head 증거, 승인, 보안 및 운영 릴리스 기준을 추가했습니다. README와 CLAUDE.md의 문서 권위 규칙을 단위 테스트로 검증합니다.
현재 상태 및 문서 기준 ARCHITECTURE.md, README.md	미해결 아키텍처 공백, 개발 우선순위, 문서 링크와 현재 제공 기능·게이트된 항목의 표시 규칙을 정리했습니다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🟡 Moderate · up to 9dc7d

This documentation change is not ready to merge because CLAUDE.md still points to a removed README section, leaving maintainers with contradictory merge guidance, and the recorded validation does not clearly correspond to the current commit. The heading test and package-description mismatch also need bounded follow-up.

Suggested reviewers: cursoragent

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 보호된 develop 기준으로 런타임 권위 문서를 정리하는 주요 변경 사항을 정확하고 간결하게 설명합니다.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/reconcile-shipped-runtime-authority-20260815

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[seonghobae]

@opencode-agent
@cwl-noema-review

Fresh exact-head review request for 9e307e559e8daa4aa0309b2e9aa62d301b452d91 against unchanged protected develop@b88e66e81e9701404d29a0f5de4f58573ceee14f. This PR changes only AGENTS.md, ARCHITECTURE.md, and README.md to reconcile canonical authority with already-shipped runtime behavior; all six repository-native workflows are terminal-success on this exact head. Review only the exact current head, verify no active-PR behavior is promoted to shipped truth, and publish current-head evidence. Do not mutate or merge.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[seonghobae]

@opencode-agent review

Please submit a formal review for exact current head 36c47db9ee6071c5ba9aaa1685fb547ac60c5a2e against protected develop@44e7903cf8891c65410f7fc6ca5144de3fdb5185. This is documentation-authority reconciliation only. Verify AGENTS.md, ARCHITECTURE.md, and README.md describe the protected Node/Hono + SQLite runtime and standalone profile without promoting active-PR features to shipped truth, preserve the protected toast asset/runtime contract, keep contextual-orchestrator production fail-closed behavior accurate, and do not retain obsolete fixed PR merge maps or stale task-state ownership claims. Review only; do not mutate, merge, weaken gates, or transfer predecessor-head evidence.

[devin-ai-integration]

Devin Review found 3 new potential issues.