Prepare the admin template for open-source reuse#5
Merged
Conversation
Opening the template to external users requires more than working code: consumers need a license, environment example, contribution and security expectations, release notes, and package metadata that describe ownership and support surfaces. This adds those project files and documents the production security boundary so frontend RBAC is not mistaken for backend authorization. Constraint: Keep the project installable with the existing npm workflow and avoid adding runtime dependencies. Rejected: Leave the PostCSS advisory as documentation only | npm overrides can pin the transitive package to a patched version without changing Next APIs. Confidence: high Scope-risk: narrow Directive: Remove the PostCSS override once Next depends on a patched PostCSS release directly. Tested: npm audit --omit=dev --registry=https://registry.npmjs.org Tested: npm run verify Not-tested: Fresh npm ci on GitHub-hosted Linux after push. Co-authored-by: OmX <omx@oh-my-codex.dev>
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.
Opening the template to external users requires more than working code: consumers need a license, environment example, contribution and security expectations, release notes, and package metadata that describe ownership and support surfaces. This adds those project files and documents the production security boundary so frontend RBAC is not mistaken for backend authorization.
Constraint: Keep the project installable with the existing npm workflow and avoid adding runtime dependencies.
Rejected: Leave the PostCSS advisory as documentation only | npm overrides can pin the transitive package to a patched version without changing Next APIs.
Confidence: high
Scope-risk: narrow
Directive: Remove the PostCSS override once Next depends on a patched PostCSS release directly.
Tested: npm audit --omit=dev --registry=https://registry.npmjs.org
Tested: npm run verify
Not-tested: Fresh npm ci on GitHub-hosted Linux after push.