Turn an explicitly authorized role invocation into a supported GitHub operation.
- Validate exact package, binding, target and permission.
- Request private repository creation, snapshot push or declared issue/PR operations.
Deletion requires an exact grant and backup declaration. Public visibility changes, force pushes and permission-setting changes are outside the implemented operation set.
Package distribution is not activated by this documentation. Use the checked-in source and the declared dependency versions; published availability must be verified separately.
Install Rust 1.97 or newer and make the declared dependencies available. Resolve the declared library dependencies from crates.io. Run from this repository:
cargo test --lockedImplementation and public interfaces · Verification cases · Contributing · Security reporting · License · Attribution notices
The worker uses --zixcel-github-transport and --zixcel-transport-config to
select the GitHub provider executable and its owner-private configuration.
GitHub egress contracts resolve from crates.io. HAT specifications also resolve from crates.io. Caller
authorization must name the exact zixcel-github-transport audience; no
credential, implicit permission, or provider mutation is supplied by this worker.
OSS responsibility and source completion defines the supported package boundary and required acceptance. It does not declare unexecuted source, distribution or production checks complete.
Dependency updates: repository policy.
The current source package has no linguistic clause frames. Its catalog and foundation dependency digests follow the declared HatSpec source dependency. This source change does not replace previously signed release bytes. A new immutable release identity and consumer acceptance are required before distributing the changed package; language meaning/adoption remains with sem-lang.