Module provenance 

Which version of the Prometheus Skill Pack is loaded.

Why this exists

UAR pinned the skill pack at a commit that was 359 commits and two months stale, exposing 161 skills where the pack had 220 — and nothing detected it, because nothing recorded which version had been loaded. A consumer cannot notice drift from a version it never reads.

Why it never shells out to git

The obvious implementation is git rev-parse HEAD against the submodule. That is wrong for the case this runtime exists to serve: a phone has no git binary and no .git directory, and an embedded build may ship the skills as bundled assets with no repository at all.

So the pack records its own commit at generation time — the one moment a git binary is guaranteed present — into SKILLS.md’s YAML frontmatter. This module only reads that. It is a file read, and works anywhere a file can be read.

Structs

PackProvenance

Provenance of the loaded skill pack.

Functions

read_provenance

Read provenance from a pack root.