feat(integration): expose authenticated delivery-attempt status HTTP

[seonghobae]

Buyer gap

Advances #130 directly after #258 by making restart-recoverable, credential-free delivery-attempt status observable through the authenticated Plugin operator HTTP boundary. This slice remains read-only and Integration-owned. It grants no provider execution, credential materialization, origin authority, DNS/IP/redirect/proxy/connect authority, or outbound HTTPS.

Reality RED and minimum product repair

The exact #258 parent had PluginDeliveryAttemptStatusApplication and its PostgreSQL repository, but hosted runtime composition did not construct them; plugin-operator-context.ts had no delivery-status route grammar; and the HTTP controller had no delivery-attempt status route.

Regression head 7398b9051c99bc39b137ea697129dba4dab57249, run 34284401430, job 102256491368, reached GitHub-hosted Ubuntu 24.04. Exact checkout, frozen install and Plugin SDK build succeeded; the signed real Nest/HTTP GET /v1/plugins/delivery-attempts/:deliveryId then returned framework 404 where the bounded contract requires the route to exist and fail closed as fixed credential-free 503 when durable status composition is absent. That is the authoritative product RED.

Production repair ccdea29238ef11a3a6866c735dc989d2b24633ad adds only the missing boundary:

• one canonical lowercase signed GET delivery-status route;
• authentication/replay consumption before status dependency access;
• server-observed raw method/URL equality with the canonical dynamic route before framework-decoded parameters reach application authority;
• fixed credential-free status-capability 503 without backend/provider reflection;
• PluginDeliveryAttemptStatusApplication and PostgresPluginDeliveryAttemptStatusStore composed over the Integration-owned PostgreSQL pool;
• real HTTP acceptance for absent composition, exact tenant/user-scoped credential-free 200 evidence, and percent-encoded raw-path alias rejection.

Verification RCA and terminal exact candidate

Verifier run 34285801146, job 102260989707, reached the product repair and passed exact checkout, frozen install, Plugin SDK build and focused HTTP + hosted-runtime acceptance at 2 files / 26 tests. It then failed canonical Prettier on the seven then-present slice/workflow files, so typecheck/full-suite evidence was correctly withheld.

The first formatter design was also repaired before execution because it would have relied on a GITHUB_TOKEN push recursively triggering a successor workflow. Current writer input fe5ef1935de941897b668da8f5aa07212f08e28e instead created the final candidate locally, retired both purpose workflows, and verified that exact candidate before publication.

Run 34287096996, job 102265083137, completed GREEN on Ubuntu 24.04. It produced exact candidate 097267ddf583b6d4d93047ff8bcfba089b1e979e, then on that exact commit passed:

• bounded Prettier repair plus prettier --check and git diff --check;
• Plugin SDK build;
• focused status HTTP + hosted-runtime acceptance: 2 files / 26 tests passed;
• Integration typecheck;
• complete Integration suite: 69 files passed / 14 skipped (83 total), 423 tests passed / 45 environment-dependent skipped (468 total).

Only after those gates passed did the writer fetch the remote branch, prove it still equalled input fe5ef193..., and ordinary-push the already-tested candidate 097267dd.... Both temporary workflows are absent from the published candidate, and the retained PR diff is now exactly six Integration source/test files. Current #259 is therefore exact 097267ddf583b6d4d93047ff8bcfba089b1e979e, open/Draft/mergeable.

This is exact-candidate product verification, not protected-main merge/release authority. Fresh independent submitted approval, applicable repository/security gates, live-base/prerequisite integration, and buyer-path performance evidence remain separate promotion requirements.

Deliberate boundary

The response exposes #258 credential-free status evidence only. Durable destination identity is not network authorization. ContextualWisdomLab/EgressWeave still publishes no immutable release, so provider HTTPS, DNS/IP/redirect/proxy/connect authority and provider execution remain fail closed.

No real PostgreSQL end-to-end/k6 p95 artifact has yet been produced for this new HTTP buyer path, so no p95 ≤ 20 ms claim is made. No owned coverage-percentage artifact was produced by this slice either.

Refs #130, #251, #252, #253, #254, #255, #256, #257, #258; ContextualWisdomLab/EgressWeave.

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