Status: IMPLEMENTED_SERVER_SIDE / CREDENTIAL_GATED

Provide a governed server-side path for publishing approved IMPERIAL Core public artifacts to GitHub without exposing credentials to agents or chat output.

• Repository: oromaskevic23-cmd/VELION-LLM-Public
• Base branch: main
• Default write mode: feature branch + pull request

Allowed paths:

• README.md, CONTRIBUTING.md, SECURITY.md, CITATION.cff, deno.json
• public_release/**, src/**, examples/**, tests/**, benchmarks/**, scripts/**, evidence/**
• docs/**
• .github/ISSUE_TEMPLATE/**, .github/PULL_REQUEST_BODY.md, .github/PULL_REQUEST_TEMPLATE.md, .github/copilot-instructions.md
• assets/velion-llm-*

Explicitly denied even if requested: .github/workflows/**, repository secrets, credentials, arbitrary root files, and any path outside the allowlist.

All other repositories and paths are denied by default.

• DENY BY DEFAULT.
• GitHub credential values must never be returned, logged, journaled, or written into repository files.
• No password, 2FA, browser cookie, session extraction, OAuth bypass, or credential reconstruction.
• No force push.
• No branch protection bypass.
• No secret-management API access.
• No write when a supported GitHub credential is absent.
• Repository metadata push=true is not proof that the current integration can write.

REQUEST -> ALLOWLIST -> CREDENTIAL PRESENCE -> BASE SHA -> CREATE/REUSE FEATURE BRANCH -> WRITE FILES -> READ-BACK -> OPTIONAL PR -> EVIDENCE -> TASK JOURNAL

A publication is PASS only when every intended file is read back from GitHub after the write and a real commit SHA is available.

The bridge accepts an already-authorized server-side GitHub credential from environment key IMPERIAL_GITHUB_TOKEN or GITHUB_TOKEN.

The skill does not create or fabricate a credential. If neither key exists, it returns EXTERNAL_GITHUB_AUTHORIZATION_REQUIRED.

Recommended credential: fine-grained GitHub token or GitHub App installation token restricted to the required repository with minimum Contents: Read and write and, when PR creation is requested, Pull requests: Read and write.

NCA may prepare files, verify hashes, execute the bridge, and validate read-back. NCA cannot expand the repository allowlist or acquire owner credentials.

USER_AUTHORIZATION_IN_CHAT != GITHUB_OAUTH_OR_INSTALLATION_CREDENTIAL

PREPARED_PACKAGE != GITHUB_PUBLISHED_PACKAGE

WRITE_RESPONSE != VERIFIED_PUBLICATION until read-back succeeds.