[Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding

Problem

The AutoGenesis 1.1.1 Skills Preview root README describes superseded Skill names and onboarding, generated-file approval and replay, and public package/Release paths that do not exist yet. It also treats intended client and platform coverage as accepted support. A public user cannot identify the one truthful Preview route or distinguish qualified evidence from experimental compatibility.

User outcome

A public user can understand one canonical autogenesis Skill plus standard stdio MCP, but is told to wait until immutable Release assets are published and accepted. After publication, Agent-first is primary and CLI-first is secondary. Direct natural-language execution and exact BDD execution remain available. Explicit recording may return a read-only preview, but generated files cannot be committed: PR #72 is integrated in main at 5030304dcaf4a4bbc04b58791345ec35016f5317 and this branch now inherits that merge.

Before publication, only maintainers and assigned independent acceptors may use the exact-head CI Candidate for release acceptance. It is not a public installation path.

Approved product position

Maximize Coding Agent reach through generic Agent Skills discovery plus standard stdio MCP.
Publish one canonical Skill named autogenesis; do not create client-specific Skill variants or compatibility adapters without evidence of a real blocker.
Present Agent-first onboarding as primary and CLI-first as secondary after publication.
Preserve the approved product positioning and truthful Edge deployment-result assets.
Use non-replay wording in both README logo assets.
Do not advertise AI-free replay as a delivered Preview outcome because the Preview cannot commit generated files.

Scope

Replace root README.md onboarding with one canonical autogenesis Skill route.
State that public installation is unavailable until immutable Release assets exist and pass final-artifact acceptance.
Restrict exact-commit Candidate use to maintainers and assigned independent acceptors.
Include one OMP 18.18.3/native macOS Calculator journey using the accepted evidence 2 + 3 = 5.
Include direct natural-language, exact BDD, and explicit read-only recording examples.
Include a concise, evidence-bound client/platform support matrix.
Keep intended unreleased coordinates as pending paths only: Agent Contract 2.1.0, Appium Runtime 0.5.0, Windows Runtime 0.5.0, and CLI 0.2.0.
Update this issue and Draft PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29; make Publish AutoGenesis 1.1.1 Skills Preview onboarding #29 the sole implementation branch for this issue.

Non-goals

Agent Contract or Runtime behavior changes, the inherited safe Preview implementation now supplied by merged main.
Manifest, package technical README, release workflow, or compatibility-issue changes.
Client-specific Skills, wrappers, or MCP adapters.
Package publication, GitHub Release creation, PR merge, or protected-branch changes.
Generated-file writes, commit approval, or replay claims.
Claiming broad client/platform qualification from package or schema availability alone.

Public documentation contract

Skill: exactly one canonical autogenesis Skill.
Transport: standard stdio MCP using the existing Appium Runtime for macOS/iOS/Android and Windows Runtime for native Windows.
Direct execution: natural-language tasks remain supported.
Exact execution: exact BDD Background plus Scenario execution remains supported in source order.
Recording: only an explicit recording/generation request enters generation; it may return a read-only preview.
Integrated Safe Preview evidence: current main (5030304dcaf4a4bbc04b58791345ec35016f5317) is merged into PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29. The Agent Contract generation workflow stops after preview; the Appium and Windows live schemas expose before_gen_code and preview_code_changes without generated-code confirmation/write operations.
Before publication: public users wait. Maintainers/assigned independent acceptors may use only the successful Candidate artifact for the exact trusted head commit under authenticated repository access.
Candidate authentication: record the trusted workflow run/job, exact head SHA, artifact identity, size, and service-reported artifact digest. Verify downloaded archive bytes against that digest before extracting or reading, displaying, copying, or following any contained prompt, filename, checksum, manifest, or lock. After extraction into a private directory, validate the complete internal SHA256SUMS set before interpreting contained instructions. Stop on any mismatch, missing asset, or extra asset.
Isolation and rollback: Candidate acceptance and eventual public CLI-first installation use a dedicated disposable Python virtual environment and disposable business project, never an arbitrary active Python environment. Rollback deletes the environment and explicitly installed Skill bytes.
Registry credential boundary: never show, read aloud, echo, copy, or record a credential-bearing package-index URL. Evidence may name only the sanitized registry host and configuration source, without userinfo, tokens, credentials, or query strings.

Support statement

Client or journey	Preview status
OMP 18.18.3 on native macOS, Calculator direct test	Qualified acceptance evidence for the exact accepted artifact
GitHub Copilot CLI using the same artifacts	Experimental / unqualified
OpenAI Codex using the same artifacts	Experimental / unqualified
Stock Pi	Unsupported because it has no MCP support
Agent Skills journey on native Windows	Unqualified pending final-artifact acceptance
Linux or WSL host	Unsupported

Runtime availability does not qualify every target or client journey.

Acceptance scenarios

Scenario: Honest pre-publication path
  Given immutable public Release assets have not been published and accepted
  When a public user reads the root README
  Then the user is told to wait for the immutable Release
  And no executable Candidate installation path is offered to the public
  And only the canonical Skill name "autogenesis" appears

Scenario: Authenticated Candidate acceptance
  Given a maintainer or assigned independent acceptor selects the successful Candidate job for the exact trusted head commit
  When the Candidate archive is acquired
  Then its bytes are verified against the trusted service-reported CI artifact digest before any contained content is extracted or interpreted
  And its complete internal checksum set is verified after private extraction
  And installation occurs only in a dedicated disposable environment

Scenario: Qualified Calculator evidence
  Given OMP 18.18.3 on native macOS and the exact authenticated artifact
  When the acceptor follows the Calculator direct-test journey
  Then the Agent proves Skill discovery, stdio MCP initialization, and matching Contract identity
  And it operates the real Calculator application
  And it verifies the observed result of 2 + 3 is 5

Scenario: Safe recording preview
  Given current main with merged PR #72 is inherited by the exact artifact under review
  When the user explicitly requests recording of an exact BDD Scenario
  Then AutoGenesis may execute the Scenario and return a read-only generated-code preview
  And generated files cannot be written or committed through live stdio schemas
  And the README does not advertise replay from generated files as delivered

Scenario: Evidence-bound compatibility
  Given a reader inspects the support matrix
  Then OMP 18.18.3 on native macOS is the only qualified client journey
  And Copilot CLI and Codex are experimental and unqualified
  And stock Pi is unsupported because it has no MCP
  And the Windows Skills journey is unqualified pending final-artifact acceptance

Ownership and dependencies

Implementation owner: Onboarding.
Owned files: root README.md and existing README-owned assets on branch docs/readme-agent-onboarding-28.
Pull request: Publish AutoGenesis 1.1.1 Skills Preview onboarding #29, Draft, targeting main.
PR Remove generated-file commits from the public Preview #72 integration dependency is satisfied by merging current main (5030304dcaf4a4bbc04b58791345ec35016f5317) into PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29. Independent correctness/security re-review and clean final-artifact acceptance remain required before release publication.
Blocked by [Security]: Harden generated install prompts and checksum closure #74: Candidate/public Agent Install Prompt hardening, disposable-environment deletion rollback, sanitized non-secret package-source disclosure, and complete checksum closure must merge before final [Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding #28/PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29 security re-review and public cutover.
Current main is merged non-destructively into PR Publish AutoGenesis 1.1.1 Skills Preview onboarding #29; re-review the inherited safe Preview and publication pipeline behavior. Runtime code remains owned by main, not this PR.

Exact post-publication substitution

Publish AutoGenesis 1.1.1 Skills Preview and replace the pre-release warning and acceptance-only guidance only after the immutable agent-contract-v2.1.0 GitHub Release contains this complete reviewed asset set with recorded SHA-256 values:

agent-install-prompt.txt: immutable URL and SHA-256;
autogenesis-SKILL.md: immutable URL and SHA-256;
release-manifest.json: immutable URL and SHA-256, containing exact filename, version, byte size, immutable URL, platform set, and SHA-256 for each reviewed wheel: autogenesis-agent-contract==2.1.0, autogenesis-appium-mcp==0.5.0, autogenesis-windows-mcp==0.5.0, and autogenesis-cli==0.2.0;
autogenesis-release.lock: immutable URL and SHA-256; and
SHA256SUMS: immutable URL and SHA-256, with entries matching the exact Skill, Release manifest, and Release lock bytes.

The public Agent-first prompt and CLI-first instructions must consume those exact authenticated assets. CLI-first must create and install only in a dedicated disposable virtual environment and document deletion of that environment plus explicitly installed Skill bytes as rollback. Neither route may expose a credential-bearing package-index URL. Remove the not-public warning only after clean final-artifact acceptance confirms the published bytes, integrated safe Preview boundary, and advertised support tiers.

README redesign evidence for commit ce18d59 / PR #29

Independent code review: APPROVE.

Confirmed package names, versions, entrypoints, Skill role split, readiness conditions, status disclosures, links, and exact gated CLI sequence.
Initial findings for Windows status, bootstrap approval, and physical-iPhone readiness were remediated and re-reviewed.

Independent security review: APPROVE.

Agent Install Prompt now requires exact-plan approval before process execution, network access, or filesystem writes, with fresh approval after any change.
It preserves conflicting existing content and fails closed on shadowing, ambiguity, transformed bytes, digest/Contract mismatch, or inability to prove the discovered path and identity.
The unpublished public package coordinate is explicitly prohibited; exact future CLI commands remain inline documentation, not a runnable shell block.

Prompt eval comparison

Harness: same session slow model for baseline and candidate; independent structured grading.
Fixed cases: approval before fetch, conflicting shadow Skill, changed plan, and unprovable discovery resolution.
Baseline (c7ff16e): 3/4.
Candidate (ce18d59): 4/4.
Regressions: 0.
Candidate improvement: an agent unable to prove the resolved Skill path/digest/version stops instead of reporting installation success.
Raw local evidence: /tmp/autogenesis-readme-prompt-eval.json (synthetic paths only; no credentials).

Verification

Agent Contract Skill/release tests: 18 passed.
Generated Agent Install Prompt matches the README block byte-for-byte.
GitHub GFM render completed successfully.
All 11 repository-relative links resolve.
autogenesis --help and autogenesis install --help matched the documented interface in an isolated verifier environment.
git diff --check passed.

Human Product Owner acceptance remains pending through OMP, Codex CLI, Pi, and GitHub Copilot CLI. Public package/release publication and native Windows acceptance remain gated.

Human Product Owner rejected the first README candidate and approved a new product direction.

Core positioning:

Write the behavior. Watch AI record it. Replay without AI.

AutoGenesis lets development and QA teams describe test cases in BDD natural language. A Coding Agent uses MCP to execute the case against the real application and records the observed calls into generated test code. The resulting case can replay without AI. The product supports Windows, macOS, iOS, and Android.

Required README correction:

Lead with the user outcome and complete BDD-to-replay workflow, not packages or governance mechanics.
Show the difference between AI-assisted recording and AI-free replay.
Explain developer, QA, and CI collaboration.
Keep Agent-first setup primary and demote CLI, package versions, trust mechanics, and Runtime details.
Do not route new users through stale clone-based documentation.
Keep release and compatibility status accurate but below the product story.
A real Hero Demo will be designed and added separately; the rest of the README should proceed now without a fake placeholder.

PR #29 remains unaccepted and will be revised in place.

README product redesign update — commit b66da16

The first candidate was rejected by the Human Product Owner. The revised README now leads with the approved product position:

Write the behavior. Watch AI record it. Replay without AI.

Observable changes:

Leads with BDD → exact real-app execution → observed MCP recording → preview approval → Behave replay.
Explains the development/QA/CI collaboration model before installation.
Makes Agent-first onboarding primary; CLI, package, Runtime, and trust mechanics are lower-level content.
Covers Windows, macOS, iOS, and Android without presenting pending acceptance as complete.
Removes the stale repository template and does not route onboarding through the old clone-based documentation site.
Keeps the full verified Agent Install Prompt in a collapsed reference.
Explicitly qualifies model-backed visual assertions: replay does not require the Coding Agent, while recorded visual-model checks retain their configured model dependency.
Describes actual preview bindings and arbitrary-secret detection limitations without overstating protection.
A real Hero Demo remains intentionally deferred by Product Owner decision; no fake placeholder was added.

Independent review:

Product/correctness review ReadmeProductReviewV2: APPROVE.
Security review ReadmeSecurityReviewV2: APPROVE.

Verification:

GitHub GFM and Mermaid rendering succeeded.
Every repository-relative link resolves.
The collapsed Agent Install Prompt matches generated release output byte-for-byte.
git diff --check passed.

PR: #29

FSQ-style README refinement — commit 7860e26

Human Product Owner direction: learn from https://github.com/FSQ-lab/FSQ and leave unavailable media blank until approved assets arrive.

Changes:

Adopted FSQ's product-first hierarchy: centered position, badges and navigation, complete-test position, evidence sequence, then Quick Start.
Moved Agent-first setup immediately after product proof.
Added user-facing "Go further" and contribution sections.
Reserved invisible blank slots for the approved logo, complete-test video, scenario card, execution capture, and replay evidence. No broken links, invented screenshots, or fake placeholders were added.
Preserved AutoGenesis-specific BDD, preview approval, replay/model exception, pre-release, unsupported-host, credential, and trust-boundary contracts.

Verification:

Published branch rendered on GitHub; Mermaid rendered and all four badges loaded.
Every repository-relative link resolves.
Canonical Agent Install Prompt still matches generated release output byte-for-byte.
git diff --check passed.
Independent product review: FSQReadmeProductReview — APPROVE.
Independent security review: FSQReadmeSecurityReview — APPROVE.

PR: #29

AutoGenesis brand logo — commit 07e66a6

Added original responsive light/dark SVG wordmarks and installed them in the README using <picture> color-scheme selection.

Concept:

Three nodes represent readable BDD behavior steps.
Their paths converge into the generated executable test.
The surrounding arrow represents approved replay and the regression loop.
Typography, loop silhouette, and neutral palette relate the mark to the FSQ family without copying FSQ's shield/check symbol.

Verification:

Both SVGs parse as standalone 520×120 assets.
No scripts, external images, links, or embedded raster data.
Published GitHub README selected the dark variant correctly; image loaded with 420×96.9 rendered bounds and useful alt text.
Independent design review AutoGenesisLogoReview: APPROVE; desktop/mobile/260 px legibility and contrast checked.

Remaining media intentionally blank: complete-test video, Scenario editorial card, execution capture, and preview/replay evidence.

Scoped Edge deployment evidence — commit ba850ef

Human Product Owner confirmed the authoritative public figures and scope. README now presents only:

2.30M test steps executed in the reported 30-day period.
3,193 hours saved in the monthly operating period.
4 platforms: Windows, macOS, iOS, and Android.
99.7% pass-rate consistency.

The section explicitly attributes these to application of the approach on the Microsoft Edge browser product line and states that they are observed deployment results, not projected savings or a universal benchmark. Conflicting draft figures and all other internal PDF claims were excluded.

Verification:

Published GitHub README renders the four-column table and Edge results navigation anchor correctly.
Search confirmed no excluded 1.70M / 2,342 / 107 issues / 700+ / 413 PR / pipeline / flakiness claims.
git diff --check passed.
Independent EdgeMetricsReadmeReview: APPROVE against the supplied PDF and Human Product Owner correction.

PR: #29

Edge deployment proof redesign — commit 58eabb4

Replaced the plain metric table with a high-impact production-scale panel:

2.30M and 3,193 are the dominant first-tier results.
4 platforms and 99.7% consistency form a supporting second tier.
Blue/violet/green accents tie the Edge deployment proof to the AutoGenesis visual system.
An original browser/deployment glyph establishes context without copying the trademarked Microsoft Edge product icon.
README retains truthful Microsoft Edge text and the Microsoft trademark notice.

Responsive delivery:

Desktop asset: 1120×480; GitHub rendered at 838×359.
Mobile asset: dedicated stacked 720×950 composition selected below 480 px; GitHub rendered at 324×428 with no overflow.
Both variants contain no scripts, external resources, links, raster data, or event handlers.
Complete metric prose and descriptive alt text remain outside/alongside the graphic.

Independent EdgeImpactPanelReview: initial mobile microcopy blocker fixed; final verdict APPROVE.

PR: #29

README integration update — 090dcb2

Completed:

rebased/integrated current origin/main (7bc9af2);
corrected onboarding for published Contract 2.0.0 / CLI 0.1.0 / Runtime 0.4.0 coordinates;
all package commands retain the machine-configured package index and do not bypass its mirror/trust policy;
removed the link to the older v2.0.0 release prompt; the strengthened inline prompt is the sole Agent-first copy source;
added mandatory post-CLI Skill enumeration, shadow/conflict rejection, and resolved path/bytes/Contract proof;
updated macOS, mobile, and Windows Runtime references so local wheels are maintainer-only;
agent-contract/tests/test_skills.py: 18 passed;
generated prompt matches the inline README block byte-for-byte;
all 11 repository-relative links resolve;
pushed GitHub render verified: logo, Mermaid, Edge panels, navigation, collapsed prompt, configured-index warning, and CLI identity checks are present.

Independent final product/code review: APPROVE.

Independent security review: REQUEST_CHANGES on one release-integrity blocker. The official immutable agent-contract-v2.0.0 release still contains the older prompt bytes, while the branch generator now emits the strengthened prompt under that same release identity. Unlinking and warning in README mitigates the primary path but cannot revoke or reproduce the existing official asset.

Required before merge: publish the strengthened prompt under a new immutable identity (prompt-only version or new Contract release), update README/generator/workflow/tests to that identity, and explicitly mark the old prompt superseded. This is a Human Product Owner release decision; PR #29 remains unmerged.

README update condition audit completed after #61. PR #29 is Draft/blocked pending an approved immutable release identity and actual published coordinates for the single canonical autogenesis Skill. Retain the approved product story and media; replace all Setup/Run, Contract 2.0.0, CLI 0.1.0, and AutoGenesis 1.1 onboarding claims only when a release owner supplies verifiable coordinates. #51 limitations must remain explicit. No documentation-only workaround may assign or imply publication.

Fresh post-#74 merged-main Candidate — build passed

Approved merged main commit: 24c8b26798c5b308993d724e8ec8209972ba844b (PR #75 merge).

Quality Gates run: https://github.com/FSQ-lab/AutoGenesis/actions/runs/43041771738
Workflow attempt: 1
Candidate job: 130595149524 — passed
Artifact ID: 13865373311
Artifact name: autogenesis-candidate-43041771738-1-24c8b26798c5b308993d724e8ec8209972ba844b
Artifact size: 411926 bytes
GitHub service digest: sha256:3a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eec
Expired: false; expiry: 2027-02-09T14:46:48Z
All four run jobs passed: exact Candidate channel, documentation build, Python syntax, and extension build.

This 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.

Clean post-#74 Candidate acceptance — BLOCKED before installation

Independent acceptor used exact Candidate run 43041771738, attempt 1, commit 24c8b26798c5b308993d724e8ec8209972ba844b, artifact 13865373311.

Passed before the blocker:

GitHub artifact identity, unexpired state, name, size 411926, and service archive digest 3a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eec matched before extraction.
Complete internal checksum closure passed with no missing or extra assets.
Contract identity: 2.1.0 / c3c87437b140520e9e3d502e0ac52a1f11c532df8ac8f64847f775fec1fb533f.
Canonical Skill SHA-256: 99e276bde9c95996d9d19c8f548eac41305cea61494a3955c4c6f44563f88f64.
Candidate manifest SHA-256: 7a1a3281480cfa264d74168d9b08de07bad16c0323380f98c7e12e79b40406c7.
Install prompt SHA-256: 230578dad5a11068fcfe9400f1a57b137b767f7ac2b9846613917b59e8b0316d.
SHA256SUMS SHA-256: 4725fd1c071816dbbf1705ddfbfd537276d452df6cc7d412741ade11286e3919.

Observed blocker: the explicitly approved unauthenticated pypi.org / default-public interface 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_*, or UV_* 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.

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, class user-approved. All other Candidate identities, isolation controls, and acceptance scenarios remained unchanged.

Independent acceptor evidence:

exact artifact 13865373311 was authenticated and downloaded again;
archive size 411926 and SHA-256 3a61ae9164bed87cdcbb899f167041d74156992396a9fa3f7b95882f547c1eec reverified before extraction;
complete nine-asset checksum closure passed again; SHA256SUMS SHA-256 4725fd1c071816dbbf1705ddfbfd537276d452df6cc7d412741ade11286e3919;
fresh root reservation, exclusive lock, identity, and private ownership marker passed;
Python 3.11.8 isolated environment created;
pip used null configuration, minimal environment, transaction-owned download/cache roots, and the strict third-party hash lock; no ambient package/proxy configuration or credentials were read or used.

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.org timed 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.

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.

Navigation Menu

Repository navigation

[Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding #28

Problem

User outcome

Approved product position

Scope

Non-goals

Public documentation contract

Support statement

Acceptance scenarios

Ownership and dependencies

Exact post-publication substitution

Fresh post-#74 merged-main Candidate — build passed

Clean post-#74 Candidate acceptance — BLOCKED before installation

Clean Candidate retry — BLOCKED on approved mirror completeness

Release blocker decomposed

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Documentation]: Publish AutoGenesis 1.1.1 Skills Preview onboarding #28

Description

Problem

User outcome

Approved product position

Scope

Non-goals

Public documentation contract

Support statement

Acceptance scenarios

Ownership and dependencies

Exact post-publication substitution

Activity

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 29, 2026

houlianpi commented on Oct 30, 2026

houlianpi commented on Nov 6, 2026

houlianpi commented on Nov 11, 2026

Fresh post-#74 merged-main Candidate — build passed

houlianpi commented on Nov 11, 2026

Clean post-#74 Candidate acceptance — BLOCKED before installation

houlianpi commented on Nov 11, 2026

Clean Candidate retry — BLOCKED on approved mirror completeness

houlianpi commented on Nov 11, 2026

Release blocker decomposed

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions