Repository navigation
feat: qualify isolated supplied-content normalization across nine ingress kinds (DSE-718) - #129
Merged
Merged
Conversation
… inspection parity
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supplied documents and encoded payloads currently bypass the text-only inspection path. DSE-718 adds one Linux-first normalization/extraction profile across all nine supplied ingress kinds, preserving exact ingress hashes and deriving untrusted evidence with labeled provenance. It does not retrieve external content or grant delivery authority.
The standalone, independently hash-locked parser handles the approved text/web/data, RFC822/MIME, ZIP and conservative text-PDF profiles. A fixed immutable local Docker image runs without network, credentials or host-data mounts and with verified filesystem, capability, process, memory, CPU, time and IPC limits. Unsupported/partial/ambiguous inputs and missing controls refuse; there is no in-process fallback. Office/OCR and non-Linux worker execution remain unsupported.
normalizeemits evidence and redacted findings. Opt-inguard/inspect --normalizer-image sha256:...share raw/normalized inspection and atomic refusal. Universal mode rejects shadow/recording flags and cannot reuse legacy fail-open branches. Existing default commands retain their earlier contracts.The interview settled current formats, Linux first, supplied content only, and labeled page/member evidence where exact bytes cannot be proved. Source-map coverage is structural, not a proof of semantic extraction completeness; parser omission/compromise remains documented. Coordinator and worker require the pinned Unicode runtime.
Validation at final source
c872932b5f658dfd937332b843dff50e3264c372:sha256:db35bc1ae81bdc94ed8e849421456fb1857bed0541968ed38970825fb4f105fb: all ten packaged source/license hashes match; all three dependency wheel license sets retained. Eight actual duplicate-MIME refusal canaries and valid MIME/CommonMark positives passed.Ernest explicitly approved this security implementation and the full delivery lifecycle in the current authenticated chat. This prepares the normal v2.3.0 release through the existing signed-artifact/OIDC publishing workflow. No new external service, spend, credentials, host security-policy changes, fallback-token retirement or whole-ATK conformance claim.
CI: https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/43604913296
Normalization qualification: https://github.com/DataScience-EngineeringExperts/mcp-warden/actions/runs/43604913380
Ticket: https://linear.app/dseofficial/issue/DSE-718
Contract: docs/CONTENT_NORMALIZATION.md