[abewheel]

Completed acknowledgements were omitted from Training and Person occurrence members because Attestations have neither an operating-preparation scope specification nor an aggregate scope field. Map their canonical person and authored subjects through the shared planner, scaffold, completion writer, and validator so an existing combined acknowledgement can be reused unchanged.

Require every requested subject, the correct scoped person, completed status, eligible completion dates, and valid per-subject historical content bindings. Keep acknowledged historical revisions valid after later content changes. Also expose approved Exception expiry from its native approval.expiresOn field as a scheduled/due/overdue source reminder, preserving Program scope and closed/revoked lifecycle. Approval remains valid through the expiry day; the expired-event action appears afterward.

Publish coordinated filegrc and create-filegrc 0.20.1; model 13 and protocol 1 stay unchanged.

Validation:

• Five independent combined correctness/security review passes; final pass clean.
• Focused tests covering reconciliation, existing-proof reuse, wrong person/subject/template, incomplete status, malformed bindings, and date boundaries.
• Full Node 24 validation, package inspections, dependency audit, and private-source/secret scans.
• Fresh generated consumer with the local release package: 224 resources, zero errors or warnings.
• Own Playwright run saved and rendered a generic reconciled Person/Training occurrence using one unchanged Attestation. Browser console, network failures, and server logs inspected; own server stopped.

Release verification: protected PR CI, merged main CI, and trusted publish plus installed README smoke passed. Both npm 0.20.1 packages and latest tags were verified with registry signatures, provenance attestations bound to release commit 3a32a05fb5358dda9425b8644cbb3d49a8cacd03, and exact installed integrity.