Say when the code-health ratchet was not evaluated - #99
Merged
Conversation
PR Review — Loreframe StudioRisk: low Automated review from Findings
Changed files
CONTRIBUTING checklist
Posted by the repo PR review workflow. Re-runs on each push to the PR. |
Owner
Author
|
cursor review |
Code health
Markdown, JSON catalogs and tests are out of this table. Only Most complex functions
Trend vs baseline
Warnings
Ratchet passed. |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 3bc1e10. Configure here.
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.
Follow-up to #97.
--markdownwithout--checknow prints Ratchet not evaluated. Tests cover that preview,--checkpass, and a ratchet failure.Also refreshes
docs/development/SLICE_QUEUE.mdafter #94/#95/#97/#98.comunicaciones/remains local handoff, not a canonical source.Does not touch
useStore.ts,_launch_runtime.pyorStoryLabPanel.tsx.Note
Low Risk
Documentation and reporting-only changes to
code_health.pywith no production runtime or security impact.Overview
Markdown code-health output now states Ratchet not evaluated. when you run
--markdownwithout--check, so local previews are not mistaken for CI pass/fail. With--check --markdown, reports still end in Ratchet passed. or Ratchet failed. as before.Tests in
test_code_health.pycover all three markdown outcomes (preview, pass, failure).CODE_HEALTH.mdandSLICE_QUEUE.mddocument the flag behavior and refresh the slice queue through landed work #94–#98.Reviewed by Cursor Bugbot for commit 3bc1e10. Configure here.