feat(planning): add bounded semantic planner - #6
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.
Summary
Implements
0.2.0-dev.4 — M4 Bounded Semantic Proposal Generation.PlannerInventoryViewfrom Runtime-owned inventory factsplanner-v1promptmessage.contentValidatedPlanFreeze-gate observability corrections
parseFailurescounts only malformed JSON, schema violations, and duplicate decisionsplanner-v1now states the complete importance enum, non-empty reason rule, and positivetargetTokensruleSafety boundary
This PR intentionally does not add:
ContextManager,AgentRuntime, or the M3 Validator policyHidden units remain implicit
KEEP. Stale inventories are discarded without retry. Validator rejection stops and requires deterministic fallback.Validation
npm test: 111 passed, 1 Windows symlink-permission skipgit diff --check: cleanmain: no changes to ContextManager, AgentRuntime, MemoryStore, tool evidence, or ValidatorV020_M4_E2E_OKWith the complete schema wording, the real Qwen smoke test passed the strict protocol on its first attempt (
parseAttempts: 1, zero categorized failures). The unchanged M3 Validator then rejected one non-recoverable proposal and stopped with deterministic fallback and no mutation.Follow-up invariant
M5 must revalidate recovery-source existence and integrity immediately before any future transformation or execution.