docs(workflow-state): classify protected operability source

[seonghobae]

Problem

Normal #605 integration moved Workflow / Task Execution operability from an active candidate into protected source, but the moving commercial baseline still ended its protected-history/current-gap classification at #603 and described durable Workflow / State production evidence as only merged #542 / ADR 0013. Protected #605 now adds an observation-only exact-object read_operability producer on the existing NOEMA_WORKFLOW_STATE authority while deployed transaction/restart/recovery, representative storage-growth, p95, PITR/rollback and immutable release evidence remain open under #541.

TDD / repair lineage

• Test-only af06f70971227ccfc148563b6055ca08be47b87a requires the moving baseline to classify feat(workflow-state): expose exact-object operability evidence #605 as protected source, bind exact candidate/merge identities, name read_operability / the returned { database_size_bytes } shape, keep ADR-0013 Proposed and refuse source→deployment/recovery/p95/release promotion. Its hosted generations were cancelled by successor source before execution; no hosted RED is claimed for that generation.
• 0eb080f13c2e1eee89618e5bc1919c0fbb45d252 converged the moving baseline but contained a malformed historical fixture sentence found during self-review; e24537150a1bff3e812d1ee6b52a585b150e5f22 repaired it to the exact existing fixture identity.
• c8f29474a1fb4bde2ee576844370fee525d2bdee preserves the complete pre-convergence moving baseline byte-for-byte as docs/doctoring/product-technical-gap-baseline-history-20260911.md using the original blob b8e01a29bc422bbd29be0b34172af9e242d355d2. Its hosted application CI 34545673878, job 103097633167, is a real exact-head RED: exact checkout, live-base validation, install and typecheck passed; release tests then reported 1 failure / 4,599 passes because the new documentation regression required a standalone `database_size_bytes` code span although the canonical baseline records the stronger exact response shape `{ database_size_bytes }`.
• Current 6ad29763934e93051371f1e722bb0c233d2659c3 is the minimum causal repair: the regression now asserts the canonical returned object shape instead of an arbitrary Markdown token formatting. No baseline semantics, evidence boundary, source behavior or gate is weakened. This exact must obtain its own terminal hosted gates before Ready/merge; predecessor results do not transfer.

Boundary

Documentation-only convergence. No Workflow / Task state behavior, Policy / Approval, provider routing, Keyverse identity, quarantine/security/outbound authority, release/deployment or foreign-owner truth is changed. #605 remains source-only operability evidence; ADR-0013 stays Proposed.

Related: #541, #605, #5, #36.

Summary by CodeRabbit

• 문서

  • 제품·기술 갭 기준과 권한 규칙을 최신 보호된 기준 상태 및 Workflow/Task 운용성 근거에 맞게 갱신했습니다.
  • 외부 확장, 절차 그래프, 생명주기, 권한, 릴리스 조건 및 상업적 공백을 현재 상태와 남은 조건 중심으로 정리했습니다.
  • 승인·사전 점검 결과가 활성화 또는 게시 권한으로 승격되지 않음을 명확히 했습니다.
  • 새 기준 이력 문서를 추가했습니다.

• 테스트

  • 보호된 운용성 문서의 정확한 근거와 과장 방지 조건을 검증하는 테스트를 추가했습니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: d41b6119-92f4-4aee-8e5d-0d642c115f22

📥 Commits

Reviewing files that changed from the base of the PR and between 98942c8 and 6ad2976.

📒 Files selected for processing (3)

• docs/doctoring/product-technical-gap-baseline-history-20260911.md
• docs/product-technical-gap-baseline.md
• test/documentation-workflow-state-operability-protected.test.ts

---

📝 Walkthrough

Walkthrough

Baseline 문서가 protected source와 foreign-owner authority를 구분하고, Workflow/Task 운용성 및 external-extension lifecycle 상태를 최신 관측으로 갱신한다. Commercial gap와 release 경계를 정리하고, 문서의 식별자·관측 범위·상태를 검증하는 Vitest 테스트를 추가한다.

Changes

Baseline 문서 및 운용성 증거

Layer / File(s)	Summary
Authority 및 제품 경계 docs/doctoring/product-technical-gap-baseline-history-20260911.md, docs/product-technical-gap-baseline.md	Protected source, active candidate, transient evidence, foreign-owner authority를 구분한다. Protected main 재조회 규칙과 canonical product boundary를 기록한다.
Evidence 및 외부 확장 lifecycle docs/doctoring/product-technical-gap-baseline-history-20260911.md, docs/product-technical-gap-baseline.md	Exact-claim receipt, external-extension admission, append-only lifecycle ledger, CAS/replay, Durable Object binding, read_operability 범위를 갱신한다.
Workflow 및 procedural operability docs/doctoring/product-technical-gap-baseline-history-20260911.md, docs/product-technical-gap-baseline.md	Procedural graph, workflow-backed ACL, evaluation history, Policy/Approval CAS, publication preflight를 정리한다. Receipt의 publicationAuthorized:false와 activationAuthorized:false 제한을 명시한다.
Commercial gap, release 경계 및 검증 docs/doctoring/product-technical-gap-baseline-history-20260911.md, docs/product-technical-gap-baseline.md, test/documentation-workflow-state-operability-protected.test.ts	Commercial gap register와 GitHub Releases 0건 상태를 갱신한다. 테스트는 PR·commit 식별자, read_operability, ADR 상태, 관측 범위, 부정확한 Draft/candidate 표기를 검증한다.

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

✨ 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/workflow-state-operability-protected-20260911

---

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]

Current-head review on c8f29474a1fb4bde2ee576844370fee525d2bdee: reviewed the three-file documentation-only delta against protected main@98942c88c228c18d44808db1c29bd8f165aa4167. The moving product/technical baseline now classifies #605 as protected Workflow / Task exact-object operability source, keeps ADR-0013 Proposed, and keeps deployed transaction/restart/recovery, representative storage-growth, p95, PITR/rollback and immutable release as separate #541 acceptance. The new regression prevents #605 from reverting to Draft/candidate classification or source→deployment promotion. The pre-convergence baseline is preserved byte-for-byte under docs/doctoring/product-technical-gap-baseline-history-20260911.md; its blob is the original b8e01a29bc422bbd29be0b34172af9e242d355d2, so shortening the moving register does not discard the detailed historical RED/GREEN record. No Workflow / Task implementation, Policy / Approval, provider-routing, Keyverse, quarantine/security/outbound or foreign-owner authority changes are present. Fresh inline-thread sweep was empty before this review. No additional documentation/DDD authority finding found. COMMENT-only; not self-approval. Current exact hosted gates are still queued, so no merge authority is claimed.

[seonghobae]

Current-head review on 6ad29763934e93051371f1e722bb0c233d2659c3: re-reviewed the three-file documentation-only delta and the causal repair after hosted RED 34545673878 / job 103097633167. The failure was a formatting-specific oracle: the canonical baseline already records the stronger exact return shape `{ database_size_bytes }`, while the regression required a standalone `database_size_bytes` code span. Current head changes only that expectation to the canonical object shape; it does not relax #605 exact/merge identity, ADR-0013 Proposed status, source-vs-deployment/recovery/p95/PITR/release separation, or Draft/candidate rejection. Fresh inline-thread sweep is empty. No additional documentation/DDD authority finding found. COMMENT-only; not self-approval. Current-head hosted gates are newly queued, so no merge authority is claimed.

[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.