Uh oh!
There was an error while loading. Please reload this page.
brand: rename CivicRecords AI -> CivicSunshine (display layer) - #106
Merged
Conversation
An active commercial product (CivicRecordsOnline, PALDAM LLC) markets records- request software to the same buyer under a nearly identical name; CivicPlus also holds the CivicRec(R) mark adjacent to this space. Rename the module's public name to CivicSunshine - sunshine laws being exactly this module's domain - before any public-facing push. Scope - brand layer: - 532 display-form replacements across 93 living files (READMEs, USER-MANUAL, HTML manuals, UNIFIED-SPEC, compliance templates, doc generators, installer scripts, UI strings, and the tests pinning doc text). - The installer artifact naming contract moves together: .iss AppName/ OutputBaseFilename + release.yml build/locate steps + release-notes templates. The next release produces CivicSunshine-<version>-Setup.exe; published historical assets are untouched. - Machine identifiers unchanged: package/module ids, env vars, lowercase civicrecords URL slugs (repo redirect covers old links). Identifier migration is deferred to the next release cascade. - Historical point-in-time records keep the shipped name: dated audits, QA reports, reconciliations, findings, handoffs, superpowers specs, prior CHANGELOG entries. - GitHub repo renamed civicrecords-ai -> civicsunshine (redirects active). - CHANGELOG [Unreleased] + both READMEs disclose the rename. Verified locally: frontend vitest 42/42 pass, production build clean, release.yml artifact-name self-consistency (0 old-name refs remain). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Blockers:
- Reverted docs/ops/tier1-retrofit-ledger.{json,md} - the CO-4 ledger is a
sha256-anchored attestation of a real published release; renaming its
asset filenames made it provably false against the live GitHub release.
Proof: `check-tier1-ledger.py --live` now passes (exit 0) against the
real release page.
- scripts/check_starter_set_integration.py phrases set to the final
cross-repo wording ("CivicSunshine ... CivicMeetings"); the umbrella
starter-set release contract is updated to exactly this wording in the
companion civicsuite PR, and civicmeetings gets a one-line phrase
follow-up (its main still says "CivicRecords AI ... exchange").
Majors:
- README.md/.txt "## Status" release-history section restored wholesale
from master - every bullet is a dated, commit-anchored record and must
keep the names things actually shipped under.
- docs/deprecated/2026-04-11 SUPERSEDED + RETRACTED master-design specs
reverted - frozen audit-trail documents.
- frontend/src/pages/Login.tsx avatar badge CR -> CS (the one missed
user-visible label; app-shell badges were already CS).
Minors:
- docs/generate-unified-spec-docx.js pinnedV31 reverted to the actual
frozen archival filename on disk.
- docs/diagrams/*.svg regenerated via render_diagrams.py so the renamed
labels get correctly recomputed center anchors instead of stale
coordinates baked for the old string widths.
Verified: ledger --live PASS, vitest 42/42, production build clean.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>…e checker The synthetic umbrella contract the helper test writes must carry the same phrases scripts/check_starter_set_integration.py now requires. The real umbrella contract (CivicSuite/civicsuite docs/installer/starter-set-release- contract.md) is updated to identical wording in the companion PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…r + fixture) EXPECTED_CLERK_VERSION was stale at 1.0.1 while the umbrella's authoritative installer/modules.json declares civicclerk current_version=1.0.4 (and the civicmeetings pyproject is 1.0.4). The cross-repo --umbrella-root check would therefore fail 1.0.4 != 1.0.1 against the real umbrella. Pre-existing bug, independent of the rename; surfaced while wiring the umbrella contract rename. Fixed the constant, the required literal contract phrase, the plan-print line, and the test fixture in lockstep. Proven: check against the renamed umbrella (rename/umbrella-display-names) -> STARTER-SET-INTEGRATION: SOURCE-READY, "CivicMeetings 1.0.4" PASS; fixture helper test 3 passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
An active commercial product (CivicRecordsOnline, PALDAM LLC) markets records-
request software to the same buyer under a nearly identical name; CivicPlus
also holds the CivicRec(R) mark adjacent to this space. Rename the module's
public name to CivicSunshine - sunshine laws being exactly this module's
domain - before any public-facing push.
Scope - brand layer:
HTML manuals, UNIFIED-SPEC, compliance templates, doc generators, installer
scripts, UI strings, and the tests pinning doc text).
OutputBaseFilename + release.yml build/locate steps + release-notes
templates. The next release produces CivicSunshine--Setup.exe;
published historical assets are untouched.
civicrecords URL slugs (repo redirect covers old links). Identifier
migration is deferred to the next release cascade.
reports, reconciliations, findings, handoffs, superpowers specs, prior
CHANGELOG entries.
Verified locally: frontend vitest 42/42 pass, production build clean,
release.yml artifact-name self-consistency (0 old-name refs remain).
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
🤖 Generated with Claude Code