Make benchmark and launch readiness visible#117
Merged
Conversation
Add reproducible benchmark report artifacts, npm packaging metadata, public roadmap/research docs, GitHub community templates, and a pre-launch visual identity task without changing the core skill pipeline. Constraint: Keep the core skill pipeline unchanged and prepare distribution without publishing externally. Rejected: Publishing to npm in this change | external release action was not requested. Confidence: high Scope-risk: moderate Tested: node --check scripts/benchmark-report.mjs; issue templates parsed with js-yaml; npm run benchmark:report; npm run benchmark; npm test; npm pack --dry-run; git diff --check after roadmap update. Not-tested: npm publish, live launch posts, and logo rendering because the logo is a tracked follow-up task, not an asset in this change. 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.
Summary
Make patina easier to trust before launch by adding visible benchmark artifacts, distribution metadata, and community contribution surfaces.
What changed
npm run benchmark:reportand a reproducible benchmark report generator.docs/benchmarks/.Constraints
Verification
node --check scripts/benchmark-report.mjsjs-yamlnpm run benchmark:reportnpm run benchmarknpm testnpm pack --dry-rungit diff --checkRemaining follow-ups