CLI/harness bug

Describe the bug

• CLI version:  1.0.79 
• session ID:  da7f26e3-c693-49b1-9cce-07e0b952079a 
• precise sequence above
• “ create / edit  disappeared without a stated model switch at 17:26 and persisted through  /restart ; PowerShell remained available.”

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

Diagnosis: this does not look like a credit-limit or filesystem-permission event.

The evidence points to a tool-capability change associated with model/runtime routing:

┌──────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Time (local) │ Change │
├──────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 16:26 │ Switched from GPT-5.6 Terra to Claude Sonnet 5; create and edit became available. │
├──────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 17:23 │ Switched from Claude to MAI Code Flash; only tool_search_tool was removed. │
├──────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 17:26 │ A separate tool-inventory event removed edit and create. No filesystem denial or approval rejection preceded it. │
├──────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ 18:05 │ After /restart, the runtime still explicitly reported edit and create unavailable. │
└──────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

The session continued to execute PowerShell, Azure CLI, package installs, scaffolding, and Azure Table writes after the loss. That rules out a broad permission or session-credit shutdown.

The log’s usage checkpoints also continue increasing after the tool loss; I found no “credit limit reached,” quota error, tool-denied event, or permission rejection. Current evidence supports: the active harness stopped advertising those tools and did not restore them on restart.

No source files or tests are named. Start by inspecting the session and tool-inventory records around 17:23–18:05, including the /restart transition, and compare the advertised capabilities with the model/runtime changes. Done means identifying why create and edit disappeared and verifying that restart behavior is handled consistently.