Repository navigation
Update development roadmap and stabilize Windows validation - #40
Merged
Merged
Conversation
midhatn
marked this pull request as ready for review
November 9, 2026 03:20
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.
After PRs #34–#39 merged, the roadmap still contained obsolete publication instructions. Reconcile the Unreleased notes, plan, handoff and evidence ledger with the integrated source while keeping the published 0.4.0a1 release unchanged. Make evidence-based agent engineering an explicit requirement of the active goal: research and reuse, bounded acceptance, scoped collaboration, meaningful validation, independent review, protected integration and reproducible handoff. Keep the primary OpenAI/Anthropic references in the repository.
Record main-branch protection and refresh the target-specific upstream ledgers. These changes do not extend the qualified recovery boundary or claim successful OS-reboot continuation.
Two original Windows jobs exposed test-fixture timing assumptions. Reuse the logical observation-clock pattern for one ordinary continuation test and the existing 30-second whole-fixture join guard. Keep that guard at module scope so fixtures that borrow the helper also work. Preserve all original failures and exact predecessor bytes; connect the corrected fixtures to the existing historical-source reader without weakening its assertions. Production runtime, freshness, execution clocks and task allowances remain unchanged.
Validation for
142a838de9cd8f41a1f027c13578301f11077bb7:The source-bound fixture record preserves the original failures, corrections, evidence hashes and scope. Full original hosted checks on this new head must pass before merge. No new binary release, inference/physical rerun or unrelated upstream progress broadcast is included.