Repository navigation
[Release]: Publish AutoGenesis 1.1.1 Skills Preview atomically #70
Description
Problem
AutoGenesis 1.1.1 Skills Preview has one frozen adoption contract but no accepted release unit tying its package, Skill, and Registry surfaces together. A partial publication, mismatched candidate identity, mutable/incomplete Skill release, unsafe rerun, or unsupported compatibility claim would leave users with an unreproducible or unsafe release.
User outcome
A user receives one coherent AutoGenesis 1.1.1 Skills Preview built from approved merged main: one canonical autogenesis Agent Skill discovered through generic Agent Skills, plus the existing Appium and Windows standard stdio MCP runtimes. Direct natural-language execution and exact BDD execution remain available. Explicit recording may produce a read-only preview, but no public stdio Runtime or Agent Contract path can commit generated files until #51 delivers trusted approval.
Product version and artifact identity
The public product release is AutoGenesis 1.1.1 Skills Preview. This product version is intentionally decoupled from component/package versions: it names the coherent user-facing Preview, while each independently distributed technical artifact retains its frozen semantic identity for package resolution, protocol compatibility, and immutable verification. Do not rewrite package coordinates or the GitHub tag to 1.1.1.
Frozen release interfaces
| Surface | Exact Preview identity |
|---|---|
| Agent Contract / Skill | autogenesis-agent-contract==2.1.0; one lowercase autogenesis Skill; GitHub release agent-contract-v2.1.0 |
| Appium Runtime | autogenesis-appium-mcp==0.5.0; matching MCP Registry version |
| Windows Runtime | autogenesis-windows-mcp==0.5.0; matching MCP Registry version |
| CLI | autogenesis-cli==0.2.0; console command autogenesis |
- Compatibility seam: generic Agent Skills discovery plus standard stdio MCP only. No agent-specific Skill variants or compatibility adapters.
- Generated-code boundary: live Runtime schemas omit
confirm_code_changes;before_gen_codeandpreview_code_changesremain read-only; recording stops after preview and reports generated-file writes unavailable. - No target-version public collision existed at refinement time: all four PyPI version endpoints, both exact Registry 0.5.0 endpoints, and GitHub release
agent-contract-v2.1.0returned absent/404. Change this version line only after recorded collision evidence and a new Human Product Owner decision.
Evidence-bound support claims
| Client / platform | Preview claim |
|---|---|
| OMP 18.18.3 on native macOS | Qualified path, subject to clean final-artifact acceptance for this release |
| GitHub Copilot CLI and Codex CLI using the same artifacts | Experimental and unqualified; evidence may be reported without calling either passed |
| Stock Pi | Unsupported because it has no MCP |
| Native Windows Skills journey | Unqualified until independent final-artifact acceptance passes |
A result qualifies only the exact client, version, host, target, artifact, and journey exercised.
Dependencies and role separation
- Blocked by [Capability]: Ship generated-code recording as a read-only safe Preview #69: safe Preview implementation, exact Contract/Runtime identities and pins, and independent correctness/security review.
- Blocked by [Capability]: Make AutoGenesis 1.1.1 Skills Preview publication resumable #71: immutable Skill publication, stable rerun provenance, exact/idempotent MCP Registry preflight and postverification, and independent correctness/security review.
- Blocked by [Security]: Harden generated install prompts and checksum closure #74: Candidate/public Agent Install Prompts require a newly approved disposable environment with deletion rollback, non-secret package-source disclosure, and complete externally anchored checksum closure.
- Blocked by [Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding #28 / draft PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29: root onboarding updated and reviewed against actual final public coordinates and support tiers.
- [Security] Bind generated writes to trusted approval and directory handles #51 remains open as the future trusted-write capability and is neither implemented nor passed by this Preview.
- The release operator must not be the independent security reviewer or final clean-artifact acceptor.
- A qualified independent reviewer covers release correctness and security; an independent acceptor exercises built/public artifacts from a clean environment; the Human Product Owner retains final release approval.
Intended publication path
Use the existing main-only Publish Python packages and MCP Registry metadata workflow at .github/workflows/publish-mcp-registry.yml. A single approved candidate is built and reviewed once, then the authorized release operator uses that workflow to expose one accepted release unit across:
- PyPI for all four exact distributions and versions;
- immutable GitHub Skill release
agent-contract-v2.1.0with the complete canonicalautogenesisassets and recorded digests; and - MCP Registry for exact Appium and Windows Runtime versions.
Publication itself is out of scope while refining or implementing dependencies. Do not dispatch, publish, merge, or modify protected branches as part of this issue setup.
Dispatch blockers and required controls
Prior successful run 40892135326 proves the four PyPI trusted publishers and the MCP Registry GitHub-OIDC namespace. It does not make the current workflow dispatch-ready:
- Existing
agent-contract-v2.0.0reportsimmutable:false; currentpublish-skillsdirectly creates a published release with assets and only afterward asserts immutability. Before dispatch, repository immutable releases must be enabled and [Capability]: Make AutoGenesis 1.1.1 Skills Preview publication resumable #71 must implement draft → upload all assets → verify complete set → publish → assert immutable. - The release manifest binds
GITHUB_RUN_ATTEMPT, and consumers compare it with their current attempt. GitHub rerun-failed-jobs increments the attempt, so attempt-2 rejects the reviewed attempt-1 candidate. [Capability]: Make AutoGenesis 1.1.1 Skills Preview publication resumable #71 must preserve authenticated run/commit/manifest/digest provenance while allowing later attempts of the same workflow run to consume the exact originally reviewed artifacts without rebuilding. - Registry publication is sequential Appium → Windows and lacks exact same-version preflight/postverification. [Capability]: Make AutoGenesis 1.1.1 Skills Preview publication resumable #71 must query the percent-encoded exact endpoints, publish only when absent, skip only when the public record exactly matches the candidate, fail closed on mismatch, and bounded-retry exact postverify each surface:
https://registry.modelcontextprotocol.io/v0.1/servers/io.github.FSQ-lab%2Fautogenesis-appium/versions/0.5.0https://registry.modelcontextprotocol.io/v0.1/servers/io.github.FSQ-lab%2Fautogenesis-windows/versions/0.5.0
- PyPI matrix jobs publish independently. Preserve their exact-byte preflight/skip-existing behavior so a same-candidate rerun is resumable, then exact-query all four
/pypi/{name}/{version}/jsonsurfaces before overall success.
No-partial-release rule
The release is not published, promoted, or accepted unless every public surface exists with the verified candidate identities/digests and every post-publication check passes. A failed, cancelled, or partially completed run is a failed release, never degraded success. Before dispatch, confirm immutable-release configuration, environment approvals, trusted publishers, Registry OIDC, target-version absence/exact-match state, and rollback authority.
Acceptance scenarios
Scenario: Complete Skill assets become public once and immutable
Given immutable releases are enabled
And the workflow has one reviewed candidate with all expected Skill assets
When publish-skills runs
Then it creates a draft
And uploads and verifies every asset and digest before publication
And publishes the completed draft once
And the public API reports immutable true
And no mutable, orphaned, or asset-incomplete public release remains
Scenario: The same reviewed candidate can safely resume
Given a downstream publication job failed after attempt 1 built and verified the candidate
When the operator reruns failed jobs and GITHUB_RUN_ATTEMPT increases
Then consumers reuse the exact original run, commit, manifest, and digests
And do not rebuild or substitute bytes
And exact existing PyPI or Registry surfaces are verified and skipped
And absent surfaces are published and exact-postverified
And any mismatch fails closed
Scenario: One verified candidate is accepted everywhere
Given #69, #71, #74, and #28 are accepted with required reviews linked
When the authorized release operator dispatches the existing workflow from approved merged main
Then PyPI exposes all four exact versions
And GitHub exposes immutable release agent-contract-v2.1.0 with the complete canonical autogenesis Skill assets
And MCP Registry exposes exact matching Appium and Windows 0.5.0 records
And every public filename, digest, embedded identity, coordinate, and transport metadata matches the candidate manifest
And no partial surface is reported as release success
Scenario: Public stdio artifacts cannot commit generated files
Given a clean environment installs only the published Preview artifacts
When a client initializes each public stdio Runtime and enumerates its live tools
Then confirm_code_changes is absent
And before_gen_code and preview_code_changes remain read-only
And the canonical autogenesis workflow stops recording after preview
And no Runtime, Skill, documentation, alias, or alternate stdio route offers a generated-file commit or copy/save bypass
Scenario: Qualified OMP path works from public artifacts
Given a clean native macOS environment with OMP 18.18.3
When an independent acceptor follows only published onboarding and installs only public Preview artifacts
Then OMP discovers the canonical autogenesis Skill through Agent Skills
And initializes the applicable standard stdio MCP Runtime
And completes direct natural-language execution and exact BDD execution
And explicit recording ends at a read-only preview
Scenario: Claims remain evidence-bound
Given experimental/unsupported clients and an unqualified Windows journey
When release notes and onboarding describe compatibility
Then Copilot CLI and Codex are experimental and unqualified
And stock Pi is unsupported because it has no MCP
And Windows Skills is not qualified until independent final-artifact acceptance passes
Scenario: Any publication surface fails
Given any package, Skill asset/immutability check, Registry record, identity, digest, or public-artifact check is missing or mismatched
When release verification finishes
Then the release remains failed and unaccepted
And onboarding is not promoted to the failed coordinates
And rollback is executed for every exposed surface
And the same public identity is not silently rebuilt, overwritten, or reusedRequired acceptance evidence
Link all evidence here before acceptance:
- approved merged-main commit and one workflow run URL;
- repository-setting evidence that immutable releases are enabled;
- accepted [Capability]: Ship generated-code recording as a read-only safe Preview #69 correctness/security review and safe-write-boundary evidence;
- accepted [Capability]: Make AutoGenesis 1.1.1 Skills Preview publication resumable #71 correctness/security review, including draft publication ordering, same-run attempt-2 reuse of exact attempt-1 artifacts, negative cross-run/commit/digest checks, and absent/exact/mismatch/delayed Registry verifier cases;
- accepted [Security]: Harden generated install prompts and checksum closure #74 correctness/security review plus disposable-environment, credential-canary, checksum-closure, and external-anchor evidence;
- accepted [Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding #28 / PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29 review against actual public coordinates and claim matrix;
- workflow candidate manifest covering every filename, exact version, embedded Contract identity, and SHA-256 digest;
- PyPI JSON/API evidence for all four exact versions, filenames, and digests, plus clean non-editable public-index installs;
- GitHub release URL/tag, source commit, complete asset inventory, immutable status, canonical Skill assets, and asset digests;
- exact MCP Registry GET evidence for both 0.5.0 records and their package/transport/candidate metadata;
- live stdio initialize/tool-list evidence from installed public Appium and Windows artifacts proving the safe generated-write boundary;
- clean native macOS OMP 18.18.3 acceptance for Skill discovery, MCP discovery, direct execution, exact BDD execution, and read-only recording preview;
- independent native Windows final-artifact evidence before any Windows Skills qualification; otherwise preserve the unqualified statement;
- rendered onboarding/release support table showing the evidence-bound tiers;
- Human Product Owner approval after all preceding evidence is linked.
Compilation, source-tree tests, editable installs, draft assets, experimental-client evidence, or implementer self-attestation are not public-artifact acceptance.
Security impact
This Preview deliberately reduces authority: public stdio callers can inspect generated-code previews but cannot commit generated files. Independent review must verify registration, schemas, dispatch, aliases, workflow instructions, documentation, release assets, and public packages expose no generated-write or copy/save bypass. Publication recovery must accept only the exact authenticated candidate; mismatches fail closed. Credentials and secrets must not appear in logs or evidence.
Rollback
- Before any public write: cancel the workflow and publish nothing.
- If Skill draft upload/verification fails: delete the draft; do not publish it.
- If any public surface is exposed but the release unit or verification fails: do not advertise it; yank newly published PyPI versions rather than overwrite them, withdraw/deprecate matching Registry entries under Registry policy, and mark the GitHub release failed/superseded without reusing its identity.
- Restore onboarding to the last fully accepted release coordinates and record every action and remaining immutable public artifact here.
- After any public collision, corrected publication requires a new Human Product Owner version decision and a fresh complete candidate; never mutate or silently reuse the failed identity.
Non-goals
- No publication, merge, or protected-branch change during issue setup or dependency implementation.
- No implementation of [Security] Bind generated writes to trusted approval and directory handles #51 or generated-file write fallback.
- No second Skill, agent-specific source variant, or speculative compatibility adapter.
- No qualification based on source-tree, editable-install, or experimental-client evidence.
Activity
houlianpi commentedon Nov 10, 2026
Sanitized release-operations readiness matrix
Operational evidence for the pre-dispatch review; no repository/organization setting was changed.
agent-contract-v2.0.0reportsimmutable:false; current actor cannot authoritatively read/enable the repository settingpypi-autogenesis-agent-contract,pypi-autogenesis-appium-mcp, andpypi-autogenesis-windows-mcpplus the Registry environment have required reviewers;pypi-autogenesis-clicurrently lacks equivalent required-reviewer/main-only deployment protectionpypi-autogenesis-cliprotection match the other release environments, including required reviewer and allowed protected/main release branch policy, and link sanitized evidence. No environment may be treated as weaker because its job is one matrix member.agent-contract-v2.1.0Dispatch decision
#70 remains Ready but publication-blocked. The authorized release operator may dispatch only after every row above has linked evidence, #69/#71/#28 are accepted, target preflight is fresh, the rollback roster is named and reachable, and the Human Product Owner approves the release window. Missing admin visibility is an unresolved gate, not evidence that a control is configured.
[-][Release]: Publish the atomic AutoGenesis Skills Preview 2.1[/-][+][Release]: Publish AutoGenesis 1.1.1 Skills Preview atomically[/+]houlianpi commentedon Nov 10, 2026
Product Owner version decision (2026-11-10): the public product release is AutoGenesis 1.1.1 Skills Preview. Product and component versions are deliberately decoupled. Technical artifact identities remain exactly Agent Contract
2.1.0, Appium Runtime0.5.0, Windows Runtime0.5.0, CLI0.2.0, and GitHub tagagent-contract-v2.1.0; those coordinates must not be renamed to1.1.1. The issue title/body and Project Target Release now reflect the public product name while preserving the frozen technical table and verification contract.houlianpi commentedon Nov 10, 2026
Merged-main Candidate build — PASS
Verified
origin/mainat5030304dcaf4a4bbc04b58791345ec35016f5317, then dispatched.github/workflows/quality-gates.ymlexactly once with refmain.42843125727)autogenesis-candidate-5030304dcaf4a4bbc04b58791345ec35016f531713776038529false404705bytesThis provides the merged-main Candidate needed by the independent native-macOS acceptor. It is not publication evidence. The publication workflow was not dispatched and no repository setting was changed.
houlianpi commentedon Nov 10, 2026
Candidate run superseded — not acceptance evidence
Quality Gates run https://github.com/FSQ-lab/AutoGenesis/actions/runs/42843125727 (ID
42843125727) completed successfully and producedautogenesis-candidate-5030304dcaf4a4bbc04b58791345ec35016f5317, but final onboarding security re-review created release-blocking #74. #74 will change canonical prompt/checksum bytes on main.Therefore this Candidate artifact is superseded and non-accepted. It must not be used by a release acceptor, published, promoted, or cited as current final-artifact evidence. The artifact does not need deletion; its retained existence is historical evidence only. After #74 merges, build a fresh exact-main Candidate through the approved quality-gates path and repeat independent acceptance. No workflow was dispatched by this supersession record.
houlianpi commentedon Nov 11, 2026
Fresh release-control audit — dispatch remains blocked
Read-only GitHub REST inspection (no setting changes) now provides authoritative repository evidence:
pypi-agent-contract,pypi-appium-mcp,pypi-windows-mcp, andmcp-registry-publisheach require independent review, prevent self-review, and permit deployments only from exact branchmain.pypi-autogenesis-clistill has no protection rules and no deployment branch policy. It must match the other PyPI environments before release dispatch.maincurrently returns404 Branch not protected. Protected-branch enforcement required by governance is therefore absent and must be configured before publication/merge operations rely on it.This audit did not read or record credentials, change settings, dispatch a workflow, or publish anything. #70 remains publication-blocked until an administrator closes these controls and links evidence.
houlianpi commentedon Nov 11, 2026
Release-control settings — configured and verified
With explicit Human Product Owner authorization, the missing repository controls were changed and then read back through the GitHub REST API:
pypi-autogenesis-clinow mirrors the other PyPI environments: the same four required reviewers,prevent_self_review: true, and one exactmaindeployment branch policy.mainis now protected: one approving review, stale-review dismissal, last-push approval by someone other than the pusher, conversation resolution, admin enforcement, force-push disabled, and deletion disabled.enabled: true; not organization-enforced).No workflow was dispatched, no package/Release/Registry surface was published, and no credentials were read or recorded. Remaining dispatch gates still include accepted #74/#28, final Candidate/public-artifact evidence, current trusted-publisher and Registry OIDC confirmation, fresh target preflight, named release/rollback operators, and final Human Product Owner release-window approval.
houlianpi commentedon Nov 11, 2026
Fresh post-#74 merged-main Candidate — build passed
Approved merged
maincommit:24c8b26798c5b308993d724e8ec8209972ba844b(PR #75 merge).1130595149524— passed13865373311autogenesis-candidate-43041771738-1-24c8b26798c5b308993d724e8ec8209972ba844b411926bytessha256:3a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eecfalse; expiry:2027-02-09T14:46:48ZThis supersedes forbidden run
42843125727. It is Candidate-build evidence, not clean-artifact acceptance or publication evidence. A separate clean native-macOS acceptor is now executing the exact artifact under an explicitly approved disposable transaction; no package, GitHub Release, or MCP Registry publication has occurred.houlianpi commentedon Nov 11, 2026
Clean post-#74 Candidate acceptance — BLOCKED before installation
Independent acceptor used exact Candidate run
43041771738, attempt 1, commit24c8b26798c5b308993d724e8ec8209972ba844b, artifact13865373311.Passed before the blocker:
411926, and service archive digest3a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eecmatched before extraction.2.1.0 / c3c87437b140520e9e3d502e0ac52a1f11c532df8ac8f64847f775fec1fb533f.99e276bde9c95996d9d19c8f548eac41305cea61494a3955c4c6f44563f88f64.7a1a3281480cfa264d74168d9b08de07bad16c0323380f98c7e12e79b40406c7.230578dad5a11068fcfe9400f1a57b137b767f7ac2b9846613917b59e8b0316d.SHA256SUMSSHA-256:4725fd1c071816dbbf1705ddfbfd537276d452df6cc7d412741ade11286e3919.Observed blocker: the explicitly approved unauthenticated
pypi.org/default-publicinterface timed out in two bounded strict-hash staging attempts under Candidate-required null-config isolated pip. Zero final dependency artifacts were staged. No ambient proxy, package configuration, credentials,PIP_*, orUV_*values were read or used.Installation, Skill discovery, MCP initialization, Appium setup, Calculator direct/BDD/recording journeys, and live schema checks were not reached and are not represented as passed. Calculator remained closed. No Appium session/process remained. Identity-bound cleanup passed; the exact approved root is absent and the private-parent identity is unchanged.
This is an external package-source connectivity blocker, not Candidate acceptance. Publication remains blocked. A different source requires a fresh exact root and explicit source/effect approval.
houlianpi commentedon Nov 11, 2026
Clean Candidate retry — BLOCKED on approved mirror completeness
The Human Product Owner approved one source-only retry with a fresh exact 128-bit random transaction root and unauthenticated host
pypi.tuna.tsinghua.edu.cn, classuser-approved. All other Candidate identities, isolation controls, and acceptance scenarios remained unchanged.Independent acceptor evidence:
13865373311was authenticated and downloaded again;411926and SHA-2563a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eecreverified before extraction;SHA256SUMSSHA-2564725fd1c071816dbbf1705ddfbfd537276d452df6cc7d412741ade11286e3919;Observed blocker: the approved mirror provided no matching locked distribution for the environment. Zero final dependency artifacts were downloaded; no first-party package resolved from an index. No package, Skill, MCP, Appium, or application installation occurred. Calculator and all five acceptance scenarios were not reached. Identity-bound cleanup passed; the fresh root is absent, no transaction process remains, and the parent identity is unchanged.
This is the second approved source-path failure (
pypi.orgtimed out; TUNA lacked a locked distribution). Per the no-repeat rule, no further source hopping is attempted. Candidate acceptance, PR #29 merge, publication, and public-artifact acceptance remain blocked. The recommended next design decision is a separately reviewed same-run Candidate dependency-wheelhouse contract so native acceptance consumes authenticated complete bytes rather than depending on local live-index reachability; this is not inferred into #28 or #70 without a Ready issue and Product Owner approval.houlianpi commentedon Nov 11, 2026
Release blocker decomposed
Human Product Owner selected the minimum sufficient fix instead of further source hopping: #76 defines one authenticated same-run Candidate with complete strict-hash dependency wheelhouses for the exact macOS and Windows acceptance targets.
#76 is Ready in the AutoGenesis Agent Integration Project with frozen scope, interfaces, positive/negative acceptance scenarios, security/rollback boundaries, ownership, and verification. It blocks clean Candidate acceptance here; no implementation, workflow dispatch, package publication, version change, or repository setting change has occurred under #76 yet.