Status Summary
At main commit e2fee66bb83d01b9df54f436a753e524895130f3, the README calls 2.0.0-rc.9 the current release and tells consumers to require it. Package metadata also names the 2.0.0-rc.9 product train, while the Composer resolver smoke assigns that version to the checkout through a path-repository alias. Public Git tags and Packagist currently stop at 2.0.0-rc.8, so a new consumer cannot resolve the documented 2.0.0-rc.9 command. The Sample App consequently consumes dev-main, leaving the first-party examples with conflicting distribution guidance.
How to fix
Establish one truthful public distribution contract. If AI remains a versioned Composer package, publish the intended sequential prerelease and verify the documented command from a fresh stable-default Composer root against the normal public repository. If AI is intentionally source-only for this phase, update the README, package metadata, changelog, and resolver smoke to advertise and exercise that public source constraint without assigning a nonexistent release version. Keep Sample App guidance aligned with the selected contract.
The resolver check must exercise the same public constraint users copy; a path repository with a synthetic version is useful for compatibility testing but is not publication evidence.
Acceptance Criteria
- The documented AI install command resolves from a fresh stable-default Composer root using public package metadata.
- The semantic resolver check does not treat a checkout-only path alias as proof that a release is published.
- README release statements, Composer product-train metadata, changelog state, and Sample App consumption describe one consistent distribution model.
- Verification records the resolved public source reference for the advertised constraint.
Delete when
Delete this item when a fresh consumer can run the documented install command, resolve the advertised AI artifact to the expected public commit, and no first-party documentation or CI check claims an unpublished version is current.
Status Summary
At
maincommite2fee66bb83d01b9df54f436a753e524895130f3, the README calls2.0.0-rc.9the current release and tells consumers to require it. Package metadata also names the2.0.0-rc.9product train, while the Composer resolver smoke assigns that version to the checkout through a path-repository alias. Public Git tags and Packagist currently stop at2.0.0-rc.8, so a new consumer cannot resolve the documented2.0.0-rc.9command. The Sample App consequently consumesdev-main, leaving the first-party examples with conflicting distribution guidance.How to fix
Establish one truthful public distribution contract. If AI remains a versioned Composer package, publish the intended sequential prerelease and verify the documented command from a fresh stable-default Composer root against the normal public repository. If AI is intentionally source-only for this phase, update the README, package metadata, changelog, and resolver smoke to advertise and exercise that public source constraint without assigning a nonexistent release version. Keep Sample App guidance aligned with the selected contract.
The resolver check must exercise the same public constraint users copy; a path repository with a synthetic version is useful for compatibility testing but is not publication evidence.
Acceptance Criteria
Delete when
Delete this item when a fresh consumer can run the documented install command, resolve the advertised AI artifact to the expected public commit, and no first-party documentation or CI check claims an unpublished version is current.