Repository navigation
Spec: 0.1.4, the performance release (PF1 to PF8) - #145
Merged
Merged
Conversation
…ch area's measured baseline, what is fixed, what is open
shinyobjectz
force-pushed
the
perf-014-spec
branch
from
November 13, 2026 19:35
eec905c to
ca184a0
Compare
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.
docs/lightspeed.feature gains a rule for 0.1.4: each of its seven areas with a measured baseline, what is already fixed (by PR number) and what is open. No code.