Repository navigation
Make ATS-1 draft.3 the new-authoring default - #6
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f0d38637fa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } | ||
| ], | ||
| "source_commit": "6449b60c75e65eadd8e7c58a1160bf81549373f0", | ||
| "source_commit": "1efbce8dba5c733dc198c6be04dd3a03d3ca7b2f", |
There was a problem hiding this comment.
In a clean clone containing this commit and its ancestors, the recorded 1efbce8... commit is unavailable because it belongs to a parallel history rather than being an ancestor of af0168f; fetching only af0168f into an empty repository reproduces the missing object. Since verify_pack() runs git show against this value, ats skills verify emits SOURCE-COMMIT and the pack cannot be verified or reproduced after the unrelated ref disappears. Preserve the two-commit source/generation topology in the published history or bind the manifest to a reachable canonical-source commit.
Useful? React with 👍 / 👎.
| "standard_versions_supported": { | ||
| "legacy_interpretation": "1.0.0-draft.1", | ||
| "new_authoring": "1.0.0-draft.2" | ||
| "new_authoring": "1.0.0-draft.3" |
There was a problem hiding this comment.
The manifest advertises draft.3 for new authoring, but every generated host still ships ARTIFACT_RECIPES.md with the governing statement that new durable authoring resolves draft.2 and that draft.2 is the no-downgrade edition (for example, dist/skill-pack/generic/recipes/ARTIFACT_RECIPES.md:26-35). An agent consuming both the skill and its bundled recipes therefore receives contradictory version instructions and may author under the wrong normative edition; update the canonical recipe document and regenerate all host forms and hashes.
Useful? React with 👍 / 👎.
| The `ats` front door chooses the right public skill. New durable authoring uses | ||
| ATS-1 `1.0.0-draft.2`, the result stays readable as prose, and the local runtime | ||
| ATS-1 `1.0.0-draft.3`, the result stays readable as prose, and the local runtime |
There was a problem hiding this comment.
This new top-level statement is contradicted by the same README's current-version table at line 424 and by the linked current guidance, including docs/QUICKSTART.md:41-46, docs/STABILITY.md:13-56, docs/EVIDENCE.md:19-21, and all current examples under docs/examples/, which still identify draft.2 as the new-authoring edition. A reader following the README into the documented workflow is consequently instructed to select draft.2 despite the policy now selecting draft.3, so the non-historical user documentation needs to be updated as part of the cutover.
Useful? React with 👍 / 👎.
| "text_policy": { | ||
| "standard": "ATS-1", | ||
| "version": "1.0.0-draft.2", | ||
| "version": "1.0.0-draft.3", |
There was a problem hiding this comment.
When contributors run the repository's configured default pytest suite, this policy change makes existing regressions fail: tests/unit/test_fleet_policy.py:70,120,230 still require the shipped policy and CLI resolution to return draft.2, while tests/unit/test_public_skills.py:152-184 still requires every public skill to advertise draft.2. These tests are not included in the narrowed list in public-ci.yml, so the focused publication gate can pass while the full suite remains red; update the cutover assertions while retaining explicit draft.2 compatibility coverage.
Useful? React with 👍 / 👎.
1 participant
Summary
1.0.0-draft.3.1.0.0-draft.1for legacy/historical interpretation unless migration is explicit.0.5.0; this cutover does not add model authority or a mandatory semantic pass.0.1.4, bound to hardened source commit0c7d2429679d0b40b7b870b5772aaf4b0b7fbe3a.Pre-PR / finalization evidence
tools/validate_repo.py: 13/13ats skills verify: PASSThis completes the remaining authoring-default work for issue #4. Issue closure is intentionally deferred until this PR is merged and the merge-head publication gate is green.