Repository navigation
Fix lossy preset browser parsing and reconcile deployment status - #21
Merged
Merged
Conversation
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.
The lossy decomposition preset rendered
(A, B), (B, C)but the frontend flattened it into one component, causing an incorrect lossless result. Preserve component boundaries and make zero-step chase text reflect the actual result. Add a Node regression exercising the request handler and renderer, run in CI.Reconcile the README, original plans, deployment handoff and wiki with merged implementation and measured deployment state. Add a standard-library HTTP smoke script that submits complete objects from
/api/presets, checks semantic results, validates HTTPS normally and records bounded concurrency receipts. The supplied canonical CNAME resolves publicly, but its Render target returns 404; live deployment is still unverified. Preserve the separate wiki update merged in #20.Validation: 232 Python tests passed on Python 3.14; frontend Node regression passed; 15 local HTTP checks passed; local browser reproduced the old lossy-preset failure and verified the corrected spurious-tuple result; both repository diffs passed whitespace checks. Retained public failure receipts are explicitly distinguished from successful local checks. Full public browser/TLS acceptance remains pending Render setup.