Repository navigation
fix: enforce RFC3339 freshness and threaded browser harness (F02) - #90
Merged
Merged
Conversation
…oject-facts.json]
…te/manifest.sha256]
…te/src/lib/governed-context.js]
…sts/governed-context.test.js]
…ripts/browser_context_e2e.py]
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
1 participant
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.
F02 — strict governed context freshness semantics
Contract: reject malformed type, impossible calendar, non-RFC3339 syntax and unparseable required/optional dates. Explicit null allowed only on the two documented nullable date fields, not silently reinterpreted from garbage. Fail closed before CURRENT/eligible. The current runtime supports non-leap-second RFC3339 timestamps with millisecond JavaScript Date precision; do not claim arbitrary precision or new leap-second support.
Separate test-harness correction: use
http.server.ThreadingHTTPServerrather than one-connection-at-a-timesocketserver.TCPServerso browser keep-alive cannot block context tests. The server change does not alter product freshness semantics.Acceptance: actual-digest malformed/valid packet testcases; Node 22
npm ci, manifest/facts/manifests refresh;npm run check; Chromium context/browser; all current Pages portability checks; required Python/JS CodeQL; full GitHub workflow. Verify no test count or generated manifest drift; no weakening of rejection tests. Record owner policy if future leap-second support is desired.Historical outputs: preserve original Context Packets and decisions; recheck formerly accepted malformed-expiry cases, mark invalid or successor as required. No assertion of real compromise.
Status: isolated candidate, NOT MERGED pending GitHub CI and maintainer review.