feat(email-writing): add secure contextual-orchestrator tenant boundary - #1360
feat(email-writing): add secure contextual-orchestrator tenant boundary#1360seonghobae wants to merge 3208 commits into
Conversation
test: cover access-policy RBAC deny-path and circuit-breaker probe guard
…readiness-handoff Add digest-bound DiskSage readiness handoff
…sdomlab-audit-governance-fb7470 fix(email): RFC 5322 compliance in message ingest (Message-ID whitespace + In-Reply-To multi-id + unknown-zone Date)
Accessibility: announce pending project-candidate confirmation and verify the enabled, pending, and confirmed disabled lifecycle.
Remediate the cryptography Bleichenbacher advisory and synchronize frontend lock fixes for PostCSS, brace-expansion, jsdom, and Undici after full exact-head validation.
Document the organization-wide hold on code-owner review gates while ContextualWisdomLab has a single maintainer.
…' into feat/llm-email-writing-contracts-task2
…-task2' into feat/llm-email-writing-review-evidence-task3
…idence-task3' into feat/llm-email-writing-context-task4
…ask4' into feat/llm-email-writing-orchestrator-task5
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
PR governance metadata gate is not ready for
|
Superseded duplicate
This pull request is closed without merge because it is the same contributor head (
819c00050fc82617454dea5781f939a15158f071, branchfeat/llm-email-writing-orchestrator-task5) already proposed by #1359, but targetsmasterinstead of the protected integration branchdevelop.At closure, #1359 targets
develop@bc98789521d21271e84789888413c182aa111b4dfrom that exact same head. Keeping both PRs would duplicate review/check evidence and expose a 1,700-file historicalmaster...headcomparison unrelated to the bounded email-writing orchestration slice.Continue review and integration only in #1359. No commit or review evidence is discarded because both PRs reference the same contributor head.