Need
Recipe users need an immutable collector source pin, one authoritative workload bundle and one documented CLI workflow. Copying measurement logic or maintaining drifting recipe-local workloads is unnecessary.
Proposed bounded change
Add an offline manifest verifier for the existing frozen DeepSeek sparkDash examples and explicit GLM variants. The variants differ only in name and the already-supported thinking-control mapping; every other semantic field must match the base. Verify raw and normalized hashes, safe file paths, supported schema and declared budgets. No runtime resolver or model-name inference.
Document pinned Linux source installation including ARM64 prerequisites. Keep source Git SHA, actual invoked binary SHA, build context and workload hashes separate; the manifest must not contain a self-referential source commit. Use existing CLI commands as thin recipe entrypoints, including the shared policy decision path once available. Preserve failures and INCONCLUSIVE results; no retry-until-pass.
Provide a manual reviewed report template. Raw run directories, endpoints, private declarations, responses and provider labels are not automatically publishable. No uploader/exporter, serving-node changes or copied collector implementation.
Acceptance
Neutral CLI fixtures verify manifest/hash/path/schema failures and illegal variant drift. A clean Linux ARM64 source build invokes the verified bundle from another directory. Documented flows work against loopback fixtures for both recipe-specific controls. Independent reproduction and real backend qualification remain separately tracked: DeepSeek first when coordinated, GLM later, with no transferred qualification claim.
Need
Recipe users need an immutable collector source pin, one authoritative workload bundle and one documented CLI workflow. Copying measurement logic or maintaining drifting recipe-local workloads is unnecessary.
Proposed bounded change
Add an offline manifest verifier for the existing frozen DeepSeek sparkDash examples and explicit GLM variants. The variants differ only in name and the already-supported thinking-control mapping; every other semantic field must match the base. Verify raw and normalized hashes, safe file paths, supported schema and declared budgets. No runtime resolver or model-name inference.
Document pinned Linux source installation including ARM64 prerequisites. Keep source Git SHA, actual invoked binary SHA, build context and workload hashes separate; the manifest must not contain a self-referential source commit. Use existing CLI commands as thin recipe entrypoints, including the shared policy decision path once available. Preserve failures and INCONCLUSIVE results; no retry-until-pass.
Provide a manual reviewed report template. Raw run directories, endpoints, private declarations, responses and provider labels are not automatically publishable. No uploader/exporter, serving-node changes or copied collector implementation.
Acceptance
Neutral CLI fixtures verify manifest/hash/path/schema failures and illegal variant drift. A clean Linux ARM64 source build invokes the verified bundle from another directory. Documented flows work against loopback fixtures for both recipe-specific controls. Independent reproduction and real backend qualification remain separately tracked: DeepSeek first when coordinated, GLM later, with no transferred qualification claim.