Repository navigation
Fix required dependency metadata and newcomer setup - #6
Merged
Merged
Conversation
11 tasks done
tbitcs
marked this pull request as ready for review
September 18, 2026 01:44
tbitcs
added a commit
that referenced
this pull request
Sep 19, 2026
Resolve conflicts after PR #6 (dependency metadata, v1.0.1) merged: - extension.yml: keep version 1.0.1 from main; keep the 99-char catalog-trimmed description from this branch - CHANGELOG.md: combine both entry sets under 1.0.1 - Unreleased - .gitignore: union of patterns (main's .venv-*/ subsumes .venv-hatch/)
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.
The AEE extension declared engine >=1.0.0 even though its gaps command needs 1.0.2, and its dependency metadata did not expose the separate Evaluator extension clearly. This patch prepares 1.0.1 with documented tool dependencies, links both required repositories, and explains the manual installation order and current Spec Kit enforcement limits.
New-user documentation now distinguishes shell and agent commands, published releases and this unreleased patch, actual CLI settings and the unused YAML reference, gap stdout/output behavior, and manual evidence review. The starter claim contains no fictional observed result. The README links the benchmark's immutable measurements and failures without claiming a demonstrated correctness or token-saving advantage.
Validation adds the real engine and Spec Kit parser to hash-locked dependencies, covers all six adapter operations, and runs a clean installation with the pinned published Evaluator. CI expands to Linux Python 3.11/3.13 and Windows Python 3.12 while preserving the protected validate check. CodeQL and dependency review remain enabled. Local results: 19 tests, Ruff, relative documentation links, and installation smoke pass. See final-commit checks and docs/dependency-audit.md for coverage and limitations.
Spec Kit's official guide requires an Extension Submission issue for catalog corrections, not a catalog PR. The metadata-only correction is submitted as github/spec-kit#4626 and retains the existing v1.0.0 archive; this source patch is unreleased until separately reviewed, merged and tagged. Do not move existing tags. No merge or release is performed by this PR.
Final validation at
c7fe50c893b2173d0b72a8b499e69c129555e774: Linux Python 3.11/3.13 and Windows Python 3.12 tests/install smoke, required validate gate, CodeQL/analyze, and dependency-review all pass. Dependabot configuration validation passed on the preceding configuration commit. No open CodeQL alerts were returned. Latest main OpenSSF Scorecard succeeded; that scheduled/main workflow does not run against this PR head. Both exact public release URLs also passed installation and all six adapter operations locally. Benchmark PR #1 remains green; its 54 tests and 980 evidence objects/five manifests were rechecked. No merge or release performed.