docs(email): reconcile protected language and direction maturity

[seonghobae]

Purpose and scope

Correct the maturity labels for email document language and writing-direction support already implemented on protected main. Both email-output records still call this active-PR behavior; this lane updates their labels and the corresponding documentation-contract tests. The complete net delta is four existing-owned paths, with no email runtime, API, dependency, workflow, package version, transport, credential or deployment change.

Preserved lineage

The original RED documentation test and subsequent label repair remain in normal history. Latest protected-main integration is a normal, conflict-free merge. No valid predecessor delta was discarded or copied into another owner lane. Previous exact-head workflow receipts remain historical; they are not transferred to this candidate.

Current acquisition — 2026-09-07

Candidateebe7e009828dc0bde90a1fcdb15e307a37ed0d4b includes protected main0b88c16f14f51b54a87eb7164f0edfb06dd60902. The net delta is25additions/4deletions across docs/email-output.md, docs/doctoring/email-document-language-direction.md, src/emailOutputDocumentation.test.ts and src/protectedEmailDocumentationStatus.test.ts. A complete current open-PR file inventory found no competing writer for these paths. The remaining Decision under review heading now says Implemented decision; native assertions verify every other byte of the original normative doctoring content is preserved.

Regression commitd24b5d29 failed the existing maturity test on that stale heading; fixebe7e009 passed the complete three-file email metadata/documentation cohort:8tests,3.67s, unchanged configuration. Typecheck and whitespace checks passed. Full default coverage on predecessor4fc1b938 terminated exit1:875passed/8failed/883total,157files,297.10s. Seven tests exceeded the unchanged5s deadline; decorative image intent separately observed two prompt calls instead of one after another case timed out, without a proven causal explanation. All failures are preserved. Current-head full acceptance remains unproven; neither predecessor receipts nor focused success are transferred as a full pass. Logs and the preserved prior PR body are retained at /private/tmp/inkspan-pr154-current-proof.oNQXDJ.

Integration and release boundary

This documentation repair has no new runtime prerequisite and is not gated on an obsolete release number. Keep Draft until current applicable verification is acquired, then require current-head repository/central checks, resolved review findings and qualifying independent approval before protected merge. Refetch head/base and live governance immediately before lifecycle decisions; no self-approval, force push, bypass, fabricated status or weakening of gates.

Issue #118 remains the version-neutral stable-publication authority. Documentation maturity correction, local tests and eventual merge do not by themselves prove registry publication, deployed host behavior or release acceptance. Inkspan retains deterministic document behavior; hosts retain delivery, authorization, tenancy, persistence, durable audit and deployment responsibilities.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

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]

Restacked the protected-main email documentation maturity repair onto exact main@a40b9489665bed7d95af619a6079b9c51cab299a and propagated the event-specific Python matrix contract. Exact head: 4e90b181923a1dbede19f15e2baa7e9a8de08d99. Fresh local proof: focused canonical/email documentation contracts 16/16; TypeScript typecheck; full Vitest 157 files / 882 tests with 100% statements, branches, functions, and lines; Python support contract 4/4. Runtime and serialization remain unchanged. Draft and independent-approval gates remain unchanged.

[seonghobae]

@codex review

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