Land standalone readiness work and cut CivicAccess v0.3.0 - #8
Merged
scottconverse merged 8 commits intoJun 25, 2026
Merged
Conversation
Signed-off-by: Scott Converse <scott@localhost>
Signed-off-by: Scott Converse <scott@localhost>
Signed-off-by: Scott Converse <scott@localhost>
Signed-off-by: Scott Converse <scott@localhost>
Signed-off-by: Scott Converse <scott@localhost>
Bump the version surface 0.2.0 -> 0.3.0 (pyproject, __init__, public-UI badge, release script, README/USER-MANUAL/SECURITY/docs) and date the CHANGELOG [0.3.0] section, preserving the historical [0.2.0] demotion record. Captures the landed standalone-gate work: default local persistence, staff workspace, records-export contract, CivicCore v1.2.0 release-wheel alignment, and API validation guardrails. Still a sub-1.0.0 standalone readiness candidate -- not city-ready or public-use until the integrated-suite gate signs off. verify-release.sh passes: 25 tests, docs/ruff/placeholder gates, and wheel+sdist+SHA256SUMS build. Signed-off-by: Claude <noreply@anthropic.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.
What this lands
Lands the audited
stage-civicaccess-release-readiness-2026-06-05work ontomainand bumps to v0.3.0 (sub-1.0.0 honest label; the falsev1.0.0remains historical).This is Phase 0 of bringing CivicAccess into the Windows Local city-core profile.
Readiness work (from the branch)
/readyworks on a fresh install (no hidden env setup)./civicaccesswired to the accessibility review API./civicaccess/staff: saved review queue, readiness, integration contracts, records-ready export.GET /api/v1/civicaccess/reviews,POST .../reviews/{id}/records-export,GET .../integration-contracts.Release bump (this PR)
0.2.0 -> 0.3.0(pyproject,__init__, public-UI badge, release script, README/USER-MANUAL/SECURITY/docs).[0.3.0] - 2026-06-25dated; historical[0.2.0]demotion record preserved.Evidence
d8871b8): 0 findings, 25 tests, lint/docs/release/browser green.scripts/verify-release.shre-run locally on this branch: PASSED (25 tests, docs/ruff/placeholder gates, wheel+sdist+SHA256SUMS).Honest boundary
CivicAccess remains a standalone readiness candidate — NOT city-ready, product-ready, or public-use ready. The remaining promotion bar is the integrated-suite gate (prove it in the installed city-core stack), which is the subsequent integration phases, not this PR.
🤖 Generated with Claude Code