chore: prepare the secure, cost-capped v0.1.0 release#13
Merged
Conversation
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.
What this ships
v0.1.0alpha changelog and tag-only attested release pathVerification
ruff check, format check, mypy, and frozen benchmark validation: passnpm ci, full audit, production audit, build, 3 site tests, and lint: pass; 0 vulnerabilitiesCost boundary
This is intentionally one consolidated protected PR run. Standard GitHub-hosted runners are used; no larger runner or paid service is introduced. Post-merge full CI is removed, artifacts and logs retain for seven days, caches are capped at the included 10 GB with seven-day retention, stale closed-PR caches/artifacts were deleted, and every external fork workflow requires maintainer approval.
Claim limits
The self-owned fixture is infrastructure proof only. The frozen historical benchmark remains 0/20, outside maintainer validation is 0, reuse intent is 0, and complete all-attempt model cost is not yet measured. This PR does not claim accuracy, demand, revenue, or hosted readiness and does not publish to PyPI.