Repository navigation
docs(templates): standardize Opensiro brand casing - #39
Merged
xLagerFeuer merged 1 commit intoNov 17, 2026
Merged
Conversation
Correct the fork-local and original-native architecture Issue templates and guard the spelling in source-neutral template tests. Keep roadmap content and protocol unchanged.
xLagerFeuer
deleted the
docs/opensiro-brand-case-in-issue-templates-20261118
branch
November 17, 2026 21:08
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.
Scope
Correct the canonical spelling to Opensiro, not
OpenSiro, in both generic roadmap Issue templates.templates/FORK_CAPABILITY_ROADMAP_ISSUE.md— two references.templates/EXTERNAL_ARCHITECTURE_ISSUE.md— three references.tests/test_fork_roadmap_issue_template.py— spelling guards for both surfaces.CHANGELOG.md— the recently added template entry.This PR does not alter the roadmap, existing case artifacts, the framework, normative VSM semantics, or the structure of either template. The roadmap comparison and potential revised Issue layout remain a separate plan-only recommendation in chat; another agent can replace the roadmap independently.
Validation
protocolCI job validates the resulting repository.