Issue #12: capture metadata-only provider identity fixtures - #23
Draft
mark-e-deyoung wants to merge 6 commits into
Draft
Issue #12: capture metadata-only provider identity fixtures#23mark-e-deyoung wants to merge 6 commits into
mark-e-deyoung wants to merge 6 commits into
Conversation
6 tasks
This was referenced Sep 1, 2026
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.
Purpose
Advance issue #12 in parallel with the
desktop-ui-cvIncrement 0 agent, using real provider observations and refusing to fabricate missing evidence.This is a stacked draft PR on top of #22 (
docs/mvp-control-realignment) so the implementation is reviewed under the corrected Foundry control contract. Retarget tomainafter #22 is merged.Included
fixtures/raw;/api/tags-style evidence from authorized private local inventory;mainand exact corrected-weight revision;contents: read, no provider secrets, exact-SHA-pinned third-party actions, and artifact-only review output;Verified evidence
Hugging Face
For
vocaela/KV-Ground-8B-BaseGuiOwl1.5-0315:fe7563292bb52ab6c235fc3c87157e6a14017479;mainat capture:a3c224bdd97ed6de15baef3524eb590c480e0d78;README.mdis the only captured sibling with changed blob identity/size.This mechanically demonstrates: source revision drift is not automatically payload drift.
Civitai
Real TrueNAS dependency
131508now returns HTTP404; this is preserved as lifecycle/disappearance evidence.Real TrueNAS dependency
128713resolves as DreamShaper 8 / model ID 4384 / AIRurn:air:sd1:checkpoint:civitai:4384@128713, with primarydreamshaper_8.safetensorsSHA-256879DB523C30D3B9017143D56705015E15A2CB5628762C11D086FED9538ABD7FD.The legacy project filename for 128713 suggested another model, reinforcing that project/local filenames are not canonical identity when provider version/file evidence exists.
Ollama
Committed sanitized tags-style observation for
kv-ground-8b:latestwith provider-native digestfa1d74b1cd05750f3d17025f35f70272b883cf09757d771488be5cba103f7b37, GGUF/Q4_K_M/8.2B/context metadata. A genuine/api/showresponse is still missing.Verification
Exact fixture/test commit:
d24d7d7c8e0e65951cf9e42133d7e8709e509a95.Public workflow run
33476102380: PASS. It captured the live public evidence and passed the 10-test offline contract plus the fixture safety validator.Current PR head may include documentation-only commits after that tested implementation head; do not claim those alter runtime behavior.
Explicitly incomplete / next evidence gates
Do not close #12 from this PR alone. Still required:
/api/showresponse from an authorized local observer;The
agent-dispatch-privateexperiment branch currently records only a future choice betweenopenrouter-pinnedand Cloudflare Workers AI, not an exact OpenRouter model ID. Choosing an arbitrary model merely to fill the fixture matrix is out of scope.No model/checkpoint bytes, provider credentials, normalized observation schema, drift engine, scheduler, database, catalog UI, or acquisition implementation are introduced here.
Related: #9, #11, #12, #15, #18, #19, #22.