Repository navigation
MOTO v1.1.08 - #62
Merged
Merged
MOTO v1.1.08#62
Conversation
## Changes - Increased automatic brainstorm proof checks from one to two rounds when Mathematical Proofs and Paper Writing are both enabled. Proofs-only checks remain capped at four rounds, and completed-paper checks remain single-round. ## Bug Fixes - Fixed mandatory proof discovery, proof solver, and Validator context overflows failing to stop continuous proof loops. Autonomous runs now cancel sibling work, preserve a recoverable checkpoint, and show a route-specific model-context notification; repaired role settings resume without stale overflow state. Authored by Patrick White, Patrick@Intrafere.com
Signed-off-by: Intrafere Research Group <208883623+Intrafere@users.noreply.github.com>
Signed-off-by: Pat <pat@local>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Pin *.sha256 to LF so Windows checkouts keep the detached receipt digest byte-exact. - Regenerate the preflight attestation and bundle manifest from LF verifier source. - Classify the Codex websocket event-loop stall monitor as a non-retry wait. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Translate unavailable OS keyring errors into InstallationIdentityError so proof storage degrades to unqualified records instead of failing outright. - Isolate tests from the real installation-global keyring entry with a per-test in-memory identity store; add keyring-unavailable regressions. - Make the launcher Git reprobe test platform-independent. - Install frontend dependencies in the Python CI job for Vitest selector evidence. - Move RELEASE_ROOT out of job-level env (runner context is not allowed there), which made GitHub reject the release-evidence workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Relocate the credential-free compatibility evidence to syntheticlib-trade/compatibility/ and keep PLANS/ fully private. - Allowlist only the approved evidence members at the new location and guard against re-allowlisting anything under PLANS/. - Point the verifier, both workflows, tests, and rules at the new path; regenerate the verifier-hash-bound evidence members. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Make novelty the only admission gate across proof discovery, follow-up
proof rounds, failed-proof hints, proof framing, novelty ranking, rigor
discovery, the brainstorm submitter and Validators (including Lean-verified
rules and the cleanup keep list), topic selection/validation/exploration,
completion review, and paper continuation. Whole-question attacks stay
first in priority; genuinely novel incremental or indirect progress toward
the user prompt is now accepted, while known, routine, trivial, redundant,
and no-path results stay rejected. Rules updated; guard tests added.
- Number published proof-run activity in a bounded process-local journal and
add GET /api/proofs/runs/{proof_run_id}/activity so reloaded or resumed
tabs replay missed Live Activity once without driving run state
(api_contract_version build6-v120).
- Seal compile receipts over their JSON serialization; receipts sealed by
v1.1.08 over raw datetimes are accepted and re-sealed on store instead of
failing as invalid.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
App-level proof-run activity recovery (e2571d7) lists runs via GET /api/proofs/runs on every WebSocket connect. The Playwright fake backend did not mock that route, so six smoke specs failed their no-unexpected-requests assertion in CI. Return an empty ProofRunCollectionResponse-shaped collection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Formalization, tactic-script, Lean placeholder, and brainstorm proof-gate repair wording now refer to the selected target instead of a "high-impact target", and ask for the precise formal reading that best preserves the source claim rather than permitting a narrowed lemma. The Aggregator Lean route prefers the highest-impact theorem the submitter can completely prove, and relevance rationales say "plausibly helps". Adds a regression test that formalization prompts carry no contradictory narrowing guidance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Failed proof targets are no longer re-run unchanged in a separate retry pass after each completed paper. Discovery now sees unresolved targets (the brainstorm's own, or a completed paper's source brainstorms') as open targets and may link a materially different retry through a validated retry_open_target_id, which resolves or updates the original FailedProofCandidate. Discovery and rigor prompts weigh direct solutions against the 5-attempt Lean budget and fall back to the strongest provable novel piece. Also raises the default Lean proof timeout to 2000s (migrating the old 600/900 shipped defaults), and adds a Codex >15-minute known-issue warning with a safe external link to the 1.1.08 release notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A broken or unusable Lean/Mathlib workspace is now a typed repair stop (LeanWorkspaceRepairRequiredError) rather than proof feedback, a failed open target, or a spent attempt. Autonomous, Aggregator, Compiler, LeanOJ, and manual proof checks stop with a durable lean_workspace_repair_required message and keep their checkpoint; Autonomous saves the round as resumable lean_workspace_blocked. Lean-bound model calls are skipped when setup is known failed, and each proof round, rigor cycle, and final-solver attempt gives a failed setup one fresh retry first. Stored workspace failures from older builds are filtered out of attempt history, failure hints, and Live Activity. On Windows, when <data root>/lean4_workspace is too long for Mathlib's build files, the workspace moves to a per-data-root folder under %LOCALAPPDATA%\MOTO\lean and the launcher removes the unusable in-root MOTO workspace. If no short location exists, the launcher disables Lean with lean_workspace_path_too_long and the path problem is latched before any lake work. Bumps api_contract_version to build6-v121 for the new WebSocket event. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A later status write could reopen a run whose terminal event was already published (for example a repair-required stop followed by a stray "stopping" update), so the source looked busy again. The run manager now ignores status changes once a run is terminal, the frontend merge keeps a terminal snapshot over a stale same-generation one, and the repair guidance also shows when the backend ends a repair run as status "error". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- py/weak-sensitive-data-hashing (high): the OpenRouter validation state was keyed by a SHA-256 of the API key. It now keeps the validated key in memory, like rag_config already does, and compares with hmac.compare_digest, so no credential is hashed. - js/prototype-polluting-assignment (medium) and js/remote-property-injection (high, extended suite): the proof-run activity tracker stored cursors in a plain object keyed by run ID, so a run ID of "__proto__" wrote onto Object.prototype. It now uses a Map and persists the same JSON shape. Verified with CodeQL 2.27.2 locally (actions, python, javascript-typescript; default and security-extended suites): no alerts beyond those already on main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
MOTO v1.1.08
Features
Changes
%LOCALAPPDATA%\MOTO\lean) and the launcher deletes the unusable in-folder copy; proofs are disabled with "move MOTO to a short folder" guidance only if that isn't possible.build6-v121for the newlean_workspace_repair_requiredevent and terminal reason.Bug Fixes
max_output_tokensresponses.Developer Features
Modernized the removable cross-field workflow testing overlay with production-backed lifecycle, pruning-preservation, live activity log checks, and automatic proof-round coverage.
Added fail-closed SyntheticLib compatibility evidence with canonical receipts, contract tests, and isolated local release verification.
Hardened SyntheticLib contract evidence with exact unpublished-state validation, rollback-safe publication, non-destructive retained output, and expanded semantic-forgery regression coverage.
The program now adopts .claude modularized rules format for Claude Code users instead of .cursor rules format for Cursor users. If needed, the rules can be easily converted by any forks or local developers.
Authored by Patrick White, Patrick@Intrafere.com