Ollama health, installed/running inventory, model details, and guarded lifecycle actions

What the sources record

Asset file

docs/assets/screenshots/material-ollama-model-manager.png

Pixel dimensions

1,452 × 1,001 px, read from the PNG IHDR header

File size

128,903 bytes on disk

PNG encoding

8-bit truecolour (IHDR colour type 2)

Gallery output id

material-ollama-model-manager

Scene

ollama-model-manager

Capture batch

windows-ollama

Platform

windows-headless

Feature Gallery section

Local Ollama model lifecycle

Guided workflow caption

Ollama health, installed/running inventory, model details, and guarded lifecycle actions

Publication status

Published asset retained; current Windows refresh is blocked (blocked)

Current refresh gap

blocked: The manager surface exceeds the existing 1452x1001 acceptance frame by approximately 59px; the gate requires a complete in-viewport panel and therefore rejects the candidate. Required evidence: A genuine hidden-Windows-desktop capture after the acceptance viewport or surface contract is reconciled, with the complete panel, geometry receipt, and privacy receipt. Exact batch commands: node .codex/verification/verify_ollama_manager_cdp.js --port <owned-cdp-port> --p0-run-root <owned-p0-run-root> --ollama-run-root <owned-ollama-run-root> --capture <owned-p0-run-root>\captures\material-ollama-model-manager.png --receipt <owned-p0-run-root>\captures\material-ollama-model-manager.json

Alternative text

Ollama model manager showing endpoint health, installed and running inventory, model details, and lifecycle actions

The alternative text above is the Feature Gallery's own Markdown alt text for this frame, so the image describes itself identically in the wiki and here.

The interaction the harness performs

Run the attach-only verifier through endpoint health, installed/running inventory, selected details, and lifecycle controls, then retain its accepted final frame.

Fixture the capture batch requires

Owned P0 production-app fixture plus .codex/verification/fake_ollama_server.py in a separate validated owned run root.

Privacy gate the capture must pass

The verifier checks bounded loopback endpoints, semantic inventory, clipping, owned paths, and screenshot privacy.

Regenerating this capture

Run these commands in order, exactly as the capture batch records them. Placeholders in angle brackets are the verifier's own run root, fixture path and CDP port.

1. Step 1 of 1

   node .codex/verification/verify_ollama_manager_cdp.js --port <owned-cdp-port> --p0-run-root <owned-p0-run-root> --ollama-run-root <owned-ollama-run-root> --capture <owned-p0-run-root>\captures\material-ollama-model-manager.png --receipt <owned-p0-run-root>\captures\material-ollama-model-manager.json

Dated acceptance receipt

No dated receipt under docs/verification/ names material-ollama-model-manager.png. The frame is published without its own dated acceptance document; the build, interaction and privacy evidence for its batch is recorded in HANDOFF.md and in the Feature Gallery's refresh notes instead.

Where else this frame appears

• Open the PNG on its own
• Feature Gallery, where this frame is captioned
• Feature Gallery Markdown source
• Capture plan that declares this frame