Make packaged authoring references publicly usable - #100
Merged
Merged
Conversation
Public authors need semantic rules without private Service access. Use the existing public guide where available and retain the required native and AASM details in packaged references. Move dated receipts to maintainer history while preserving current support boundaries. Prepare an unpublished 0.7.1 candidate; leave catalog selection intact.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Public authors could not follow four consequential authoring routes because they pointed into the private Service repository. The packaged references now use the existing public Field catalog and Rails profile, and include the required native identity and AASM caveats where no public topic page exists.
Dated qualification receipts and redundant native source pins move to the existing maintainer history. The references retain normalization order and null semantics, compatibility checks, and the distinctions between accepted syntax, supported meaning, generated output, and observed behavior.
This prepares the unpublished 0.7.1 source candidate. CLI/API/Plan compatibility and the published 0.7.0 catalog selection stay unchanged. No release or Service documentation publication is included.
Validation:
sh script/check --cli-root tmp/cli-contract: deterministic shared package and 76 passing tests.fb45245c9030e1898f81fcafe108d877116bd752.1eee2e44504e14f7ed596f2ce3d65d27400399eefor Node 22.0.0 and 24.18.0, including the pinned CLI contract and Codex installation/discovery checks.Closes #99.