Add inactive GitHub forge normalizer payload - #218
Merged
Conversation
Deploying ystack with
|
| Latest commit: |
8c52943
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b73169a8.fabrica-6yx.pages.dev |
| Branch Preview URL: | https://codex-default-github-forge-a.fabrica-6yx.pages.dev |
Owner
Author
Codex reviewer (cross-vendor, read-only)Reviewed-head: 8c52943 CLEAN — zero unresolved Important findings. Bugs
Security
Compliance
|
Owner
Author
|
Construction publish receipt
|
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.
What this adds
This lands the immutable GitHub forge normalizer payload for Roadmap item 4. The pure jq filter validates one caller-bound, untrusted change-request snapshot and returns a generic observation for ready, blocked, closed, merged, stale, incomplete, or unknown state.
Its instruction and config content references now use the exact public core v2 content-ID and media-type domain. Colon and slash IDs are rejected, media types are capped at 127 bytes, and accepted references are checked through the public schema.
Why this is payload-first
The earlier manifest pointed to a branch-parent package commit. That reference is unavailable in a shallow CI checkout and would not remain durable after squash delivery. This revision removes the manifest instead of weakening CI or fetching remote history.
After this payload merges, a later assembly PR can create the manifest against the durable payload commit on main and add default-set selection. This PR does not add a manifest, profile entry, default-set wiring, workflow change, or live adapter.
Safety boundary
The payload is inactive, offline, and unqualified. It does not call GitHub or a CLI, use credentials, change a repository or request, grant authority or qualification, or activate a profile. Provider metadata remains opaque data and cannot decide normalized state.
Exact scope
Base: c276b42
Head: 8c52943
The final diff has exactly six paths: README, RESTORE, the normalizer payload, two append-only restore entries, the strengthened focused test, and one exact schema-import guard entry. The unmerged manifest and its restore entry are absent.
Proof