Repository navigation
chore: prepare methodology 8.0.0 migration and exact CLI skill boundary - #662
Merged
Merged
Conversation
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
Signed-off-by: transitrix <automation@transitrix.com>
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
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.
Prepare Methodology 8.0.0 under the existing closed-enum MAJOR policy: reconcile relation-spec wording, provide the pin-only 7.0 → 8.0 recipe with manual compatibility review, align current pins/PRESETS_VERSION, and preserve historical fixtures and diagnostic evidence. Both skill bundle manifests are 0.2.0; requirements-analysis floor is 8.0.0 because its required caller boundary changes.
Exact isolated caller qualification is recorded in transitrix/skills/requirements-analysis/qualification.json and caller-candidate.json: CLI 2.13.0 / diagrams 1.17.0, source f1d5f1e68df5f3df54ffc4a528e77b327dc60859, tarball SHA256 91470eb32fd83a5a6a0a601e890a17944066cab9cf69604299a499f021fcc5ff and npm integrity. Four subjects and retained controls passed (11 actual CLI invocations plus missing-tool refusal and verification-state interpretation), replay matched, all 54 installed files match the archive, and synthetic models stayed unchanged. Runtime-only npm audit reported zero vulnerabilities for this isolated installed set. The skill requires exact integrity/source/receipt match, with no unpinned download or implicit installation.
Hosted packaged UI/CLI parity passed 45 tests in Studio run 42419064679, against VSIX SHA256 9fa60bc4ab604dd11ea1d47e01e9440486205f83a4a9825179ad512c65dcb567. Its CLI was built at synthetic merge df85b60a0383c8bc2c7870c1ae954ec9adb29cae and archive SHA256 600eb7e16b5fe57e5b1c38fbe5a88b44b86102667e7c1ffeea55ef51325ba2c8. Both tracked source trees equal ba35bc45d33e61279dad576e8585f8cf419e77c9. This supports bounded source correlation, not hosted use or byte equivalence of the local archive. Direct exact-artifact parity and final merge/rebuild qualification remain separate.
Validation: doc-lint passed with four baseline catalogue/size warnings; 105 initial migration/shared-instruction tests and the updated shared-instruction suite passed; publication manifests, generated plugin parity and isolated discovery of 12 skills passed. Independent final review returned no actionable findings. The generic Codex skill validator rejects this repository's established min_version/when_to_use extensions; repository convention is preserved. Build-prerequisite and test-apparatus failures remain recorded in preparation evidence and were not labeled product failures.
Companions: Studio #754, reference adopter #101. All remain draft/unmerged. No source release, tag, publication, manual workflow dispatch, effective adopter upgrade or installation into a user product. This receipt does not claim a new assistant-host evaluation, final release qualification or whole-product acceptance.