Verify infrastructure-pinned identity and skill content; expose admin inspection #42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/protected-content-integrity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds optional protectedContent file SHA256 pins in infrastructure config, startup/pre-turn/persona/skill-reload checks and bundled admin-only /protected-content status inspection. Local settings cannot override pins. Fail closed for missing or changed files. 301 tests, typecheck/build pass. Review a9259b70b49b0b9a872ba36bca8744fa0eb9d4373f35bf50ffbc534f5d17daff: no P0/P1, existing unrelated P3 heartbeat-budget issue documented. Explicit limits: integrity-only, not sandbox or write protection; requires infrastructure-owned read-only config/files. No automatic trust enrollment, no unpinned-directory denial, no race-free read boundary. Docs explain limits. Memory isolated live worker test against configured embedding endpoint separately verified semantic ready, restart durability, conversation isolation, revision conflict and erasure; explicit reindex required for prompt readiness.