Retire legacy workspace proposals and repair radar tasks - #385
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
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.
Retire the old workspace proposals without restoring incompatible API or evaluation changes. Preserve the useful findings in one disposition document with historical claim boundaries and a bounded repair queue; private source and experiment archives remain local.
Fix the radar renderer and checked-in report to reference the existing entrypoint. Remove the misplaced application-level
--lockedflag from three radar tasks so the offline command runs; Cargo still uses--locked.Validation:
cargo make external-memory-radar-dry-run,cargo make check-docs,cargo make check-format, andgit diff --check. Local legacy archives were file-hash checked and Git bundles verified before removal. No product safety fixes are claimed by this maintenance PR.Supersedes the execution proposal in #353. Its source-backed principles are retained in the disposition and September value review; larger feature work remains a proposal.