Repository navigation
Use Townlight public names and current documentation - #24
Merged
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.
Current public documentation and display copy still used predecessor product names and outdated release status. Use the accepted Townlight names and canonical repository links while retaining compatibility identifiers, legal attribution and historical evidence.
This cleanup preserves package names, imports, versions, dependency/source pins, API routes and headers, database/service identifiers, installer identity and all signed release assets. No release tag, signature or published installer is replaced. Public display-copy expectations follow the new names; existing behavioral and security checks remain.
The umbrella documentation records the published Records + Meetings + Code + Zoning 1.4.0-beta.1 beta, its signed acceptance and manual 1.3 runtime-upgrade steps. Standalone module versions and maturity limits remain separate.
Validation: affected documentation gates, public-site contract checks, 19 suite-state/module-contract tests, generated status/topology checks and desktop/mobile landing-page checks. Repository CI applies to this exact head before merge. Protected evidence and package/operational contracts were checked against the baseline.