feat: production readiness hardening - #149
Conversation
| pub fn post(&self, segments: &[&str]) -> Result<RequestBuilder, TransportPolicyError> { | ||
| Ok(self | ||
| .client | ||
| .post(self.endpoint.with_path_segments(segments)?)) |
|
|
||
| pub async fn get(&self, segments: &[&str]) -> Result<Response, TransportPolicyError> { | ||
| self.client | ||
| .get(self.endpoint.with_path_segments(segments)?) |
| body: &T, | ||
| ) -> Result<Response, TransportPolicyError> { | ||
| self.client | ||
| .post(self.endpoint.with_path_segments(segments)?) |
Security maintainer review requested for PR #149Please review the current PR head, The remote
The source changes deliberately maintain fail-closed endpoint handling and bounded gateway-payload construction. In particular, The reviewed narrow Rust CodeQL barrier model for the successful
Detailed evidence is available in |
Summary
Integrates the validated production-readiness hardening series, including adverse-action/PII controls, Vault Transit custody and rotation, PostgreSQL RLS isolation, dispatch recovery, verified forensic pagination/cursor rotation, bounded forensic NDJSON export, offline completeness verification, and PWA memory bounds.
Local validation
Fresh disposable PostgreSQL/cross-service validation passed: migrations, compliance/Transit/RLS/dead-letter integrity, forensic keyset EXPLAIN, Node tests, TypeScript, PWA build, Go race tests, archive checks, and mobile type checking.
Notes
No production or staging systems, real external providers, Vault, Permify, object storage, or live PII were accessed. This PR intentionally does not bypass required review or required GitHub checks.