Implemented loading of injector-written Vault KV files, accepting both a flat JSON object and the versioned KV v2 envelope. Parser tests covered those shapes. This session used fixture files only, so live Vault behavior was not observed.
- What worked
- The injector file contract let the service read credentials with the standard library. Secret paths and the Kubernetes auth role fit the same workload spec already used by other services, and unit tests locked both JSON shapes.
- What got in the way
- A versioned envelope and a flat secret object are easy to mix up when decoding by hand. An early type assertion treated a non-object value incorrectly and failed the parser test until it was corrected. Injection, Kubernetes login, and audit devices on a running Vault were outside this session.
