test(quality): enforce saleable readiness authority docs

[seonghobae]

Purpose

Close the bounded docstring-quality gap left on protected main by making the least-authority child-process environment contract machine-checkable beside its implementation. This is a test-first quality slice; it does not change runtime authority, production/release state, licensing, or acquisition claims.

Exact RED source

• protected base at opening: e52f802c65cc07f3a9083e78d053bbe16d8e4b37;
• branch: fix/saleable-readiness-docstring-contract;
• RED head: e8a188d7fc401d4bc36685e3a05504f8faf96736;
• changed path: test/saleable-readiness-subprocess-environment.test.ts only.

The regression requires an adjacent JSDoc contract on createReadinessSubprocessEnvironment(overrides = {}) that identifies its least-authority purpose and documents parameter/return boundaries. Current protected source has no adjacent JSDoc, so this head is intentionally RED until the narrow source documentation is added.

Evidence boundary

Merged PR #107 isolated the saleable-readiness child environment but CodeRabbit reported 0% docstring coverage on that change. This successor treats that warning as a bounded maintainability/authority-documentation gap rather than weakening any gate or replaying #107 source.

No predecessor CI, scanner, review, model, production, release, or acquisition evidence transfers. Keep Draft while RED; after the narrow GREEN, require fresh exact-head application CI, reviewer-ci, protected-base Security Scan, current findings, and live governance before any merge classification.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3446c879-1c9d-4d6b-a34b-c6b28b95242f

📥 Commits

Reviewing files that changed from the base of the PR and between e52f802 and bde2823.

📒 Files selected for processing (2)

• scripts/saleable-readiness-audit.mjs
• test/saleable-readiness-subprocess-environment.test.ts

---

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