Repository navigation
Fix startup commands for four historical ceiling cards - #5520
Merged
Mister-Meeseeks merged 1 commit intoOct 25, 2026
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.
Four research task cards still emit a historical ceiling checker that raises
KeyError: 'complex_profile'against the selected #5413 certificate. This repairs their current CLI output: run the selected metadata baseline first, then the existing authenticated #1094/#1042 replay. The emitted expected statuses and inspection text identify the two different scopes.The original
catalog_first_stepremains verbatim. The resolver validates all entry references before changing any card, reports deliberate sparse omissions, and rejects missing/deleted or omitted staged-replacement references. Other scientific command variants remain unchanged. The legacy picker, catalogue, frozen scientific sources and selected frontier retain their bytes.This completes Open next question 2 of #5359 using Ali Romman's #5378 CLI boundary. Scope, compatibility evidence and reproduction · canonical claim and handoff.
Validation at
f02b5258e8523b311efa2b3802716c5fa8862065:{"include": []}; raw committed-byte and whitespace checks pass.Started from and refreshed canonical main
32890bc5de034ab8fc93ac88ead7279a6a416d04, priority 7. Final overlap covers 378 open PRs, 4,797 Discussion records and all 7,402 tracked in-scope notes, with complete reported coverage and no warnings. Taskportable-replayis explicitly changed to the concrete startup handoff; drawc15fe091c7821f358c79b35e885e7a0d.Limits: reference validation does not authenticate the full execution closure. A current supplier cost law, selected cold replay, full-history provenance audit and independent mathematical acceptance remain outside this repair. No new kappa is claimed. The Linux run used materialized catalogue references after an earlier sparse DrvFS inventory read was stopped for latency; no sparse-filesystem performance repair is claimed. Hosted CI is separate from the local results above.
Credit Ali Romman (#5378), Douglas Colkitt and the retained picker/checker/ceiling lineage, Mihir Srivastava (#4463/#4906/#5359), and the #1094/#1042 construction and audit contributors. Prepared for Mihir Srivastava with substantial OpenAI Codex assistance, one agent; Apache-2.0.
Hosted verification at this exact head is now complete: run 40169054266 passed. The plan job ran 446 onboarding tests (21 skips) and selected zero scientific packages; scientific replay was skipped as intended.