Skip to content

fix(v7): restore automated summoning and Windows model startup - #77

Merged
9thLevelSoftware merged 4 commits into
mainfrom
codex/restore-v7-summoning
Nov 12, 2026
Merged

9thLevelSoftware merged 4 commits into
mainfrom
codex/restore-v7-summoning

Conversation

@9thLevelSoftware

@9thLevelSoftware 9thLevelSoftware commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

Summary

Restore the self-contained, themed v7 grimoire so an AI can install the package, preserve existing configuration and memories, register Claude Code, and verify the result. Align the README with the current stdio setup on Windows, macOS and Linux.

Read grimoire → inspect and back up → install local profiles
             → merge MCP, hooks and covenant → host approval/restart
             → scoped memory + semantic recall → restart persistence

The actual Windows setup uncovered a second native-import startup stall: ready auto profiles loaded SciPy from a worker while the main thread started another worker. Preload the existing native-profile entry points before worker assembly on Windows, retaining disabled-profile isolation and POSIX lazy behavior.

Evidence

  • Before: the old grimoire omitted complete bootstrap steps; the first real restart stalled in SciPy native loading. Initial dense fallback was not accepted as semantic success.
  • After: real Claude Code 2.1.319 installed into a fresh Python 3.11 environment, configured the project, and passed store/recall/outcome, native edit hooks, restart persistence, ready dense retrieval and stable-key replay. A repeat setup preserved identical configuration hashes and unrelated settings, including a mixed hook entry. Offline verification passed; actual user configuration was unchanged.
  • Focused tests: 23 production tests plus four subtests; 13 documentation tests plus 41 subtests. Full Ruff, mypy and release inventory passed.
  • Full local regression run: 3,957 passed, 2,096 subtests passed, 76 skipped, and one documentation-extractor failure. The helper was updated to recognize Claude JSON command/args and retain actual shadow-package execution; both affected checks then passed. The original full local run was not all-green.
  • Initial PR CI exposed a platform leak in the new Windows simulation; the test now replaces only the production module's os reference. Its affected check passed, and subsequent Linux/macOS jobs passed it.
  • A later Ubuntu/Python 3.12 job returned an empty migrated recall after verifying the database record. The old assertion discarded diagnostics. It now retains the complete response with the same assertion and no retries or budget changes. One focused Windows 3.12 run, one fresh Ubuntu 3.12.15 run, and subsequent Ubuntu 3.12 CI passed, but the original CI cause remains undetermined; diagnostics are retained for recurrence.
  • Final revision f07d15d9a40718cbfd9a91937d26ed5ee0969012: all 12 GitHub CI jobs passed, including the complete Ubuntu/Windows/macOS and Python 3.10–3.12 matrix, lint, type-check and release inventory. GitGuardian passed separately. Working tree is clean.
  • Kilo review on a prior revision reported ACTION_REQUIRED: its configured BYOK API key is invalid, revoked, or lacks permission. It returned no code findings, and no Kilo check is attached to the final revision; independent review was completed separately.
  • Windows Python 3.10 also exposed floating-point cancellation in the pinned HTTP timeout calculation (2.5000000000002274 from a 2.5-second limit). The backend now deducts elapsed time from the original budget. A controlled-clock regression reproduced the exact failure, and nine backend tests plus 18 subtests passed after the fix; the strict limit assertion remains unchanged.
  • Independent code and evidence reviews found no remaining material issues. Details and explicit scenario limits: docs/release/v7/summoning-acceptance-2026-11-12.md.

Merge Danger

Door: two-way

No schema or user-data migration in this patch. Instructions preserve existing state and stop before unsupported external-storage migration.

Blast Radius: setup

Windows installations with ready local native profiles now pay their import cost at startup. Claude's protected-configuration approvals and restart boundary remain host-owned. Live OpenCode, E2B and other remote deployment paths are outside the disposable acceptance scenario.

Copilot AI balanced review requested due to automatic review settings November 12, 2026 06:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@9thLevelSoftware
9thLevelSoftware merged commit 54c1613 into main Nov 12, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants