What's wrong with this entry?
Anonymous. No account, no email.
When a session resumes and picks up a forked-skill agent, the resumption path now validates:
- The scoping record file (
.forked-skill.json) must be present and parseable - The record must name the same skill as the agent's task record
- For cold restarts, a provenance-marker witness (
.forked-skill.marker.json) must also be present and corroborate the fork identity
If any check fails, the agent refuses to resume and logs a clear error rather than running without its intended permission scoping. This prevents forked-skill agents from running with wrong or missing permission boundaries after a restart.
Evidence
Resume validation guards (search for "refusing to resume it without the skill's permission scoping")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.