brand+fix: rename CivicRecords AI->CivicSunshine + reconcile records pairing 1.6.1->1.7.3 - #179
Open
scottconverse wants to merge 1 commit into
Open
scottconverse wants to merge 1 commit into
scottconverse wants to merge 1 commit into
Conversation
…pairing 1.6.1->1.7.3 Meetings-side starter-set integration: the living surfaces (README.md/.txt usage, docs/ops/starter-set-integration.md, scripts/check_starter_set_integration.py, tests/test_starter_set_integration_helper.py) still named the old records module "CivicRecords AI" (-> CivicSunshine) and pinned EXPECTED_RECORDS_VERSION=1.6.1 while the umbrella installer/modules.json (the source this checker reads) declares civicrecords-ai current_version=1.7.3. The cross-repo --umbrella-root check was therefore failing 1.7.3 != 1.6.1; pre-existing, surfaced during the rename. Fixed the constant, the ops-doc "paired at v1.7.3", the plan-print line, and the fixture in lockstep. Kept historical records untouched (AGENTS.md, MILESTONE_*_DONE, ADR-0001, CHANGELOG, 5-lens audit). Meetings module keeps __version__ 1.0.4. App integration-bridge label "CivicRecords search bridge" left for the app-UI pass. Co-Authored-By: Claude Opus 4.8 <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
1 participant
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.
Meetings-side starter-set integration rename of the OLD records name (CivicRecords AI -> CivicSunshine) on the living surfaces (README.md/.txt, docs/ops/starter-set-integration.md, scripts/check_starter_set_integration.py, tests fixture), plus reconcile of the stale EXPECTED_RECORDS_VERSION 1.6.1 -> 1.7.3 (the real value per umbrella installer/modules.json). Historical records (MILESTONE_*_DONE, ADR-0001, CHANGELOG, 5-lens audit, AGENTS.md) left untouched. Meetings module keeps version 1.0.4.
Verified: cross-repo check vs merged umbrella main -> 'CivicSunshine pairing 1.7.3' PASS; fixture helper 3 passed.
KNOWN PRE-EXISTING (NOT this PR): the checker's EXPECTED_CIVICCORE_RUNTIME=1.2.1 disagrees with the umbrella's CivicCore 1.2.0 (modules.json + contract). This predates the rename (constant unchanged on main) and is a separate suite-wide CivicCore-baseline decision. Held for owner call before this merges.