feat: add lightweight workflow paths - #79
Merged
Merged
Conversation
MageByte-Zero
marked this pull request as ready for review
July 26, 2026 15:16
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.
Summary
Introduces a lightweight four-path workflow so small, low-risk work no longer pays the full planning and review cost.
quickfor bounded low-risk code work and direct incidenthotfixacceptance.tweaklightweight and preserves legacy Hotfix and Full contract/approval/plan/review controls.test_result: passfor short paths; direct Hotfix also proves the original symptom regression.Why
Simple requests were forced through the full exploration, specification, contract, execution-plan, and review path. This added visible latency and token cost without providing proportional safety.
Validation
npm run buildnpm testnode scripts/validate-artifacts docs/examples/add-dark-modenode scripts/validate-artifacts docs/examples/refactor-auth-boundary