[huangminghuang]

Summary

• Declare sysio.epoch::finishadv with its epoch index and emission amount.
• Register the continuation in the typed action mapping and runtime action list while preserving current upstream declarations.

Why

SYSIO now publishes operator state through a protected continuation after epoch-close mutations. The SDK must describe that ABI accurately. The declaration grants no calling authority: SYSIO rejects direct calls even with epoch-account authorization.

This interface selects no recovery policy. WIRE-392 remains a deployment prerequisite.

Validation

• The native pre-commit gate passed lint, full compilation and all 1,033 unit tests. The selected SDK strict-null and client checks also passed.
• The complete generated declaration file matches all 20 merged SYSIO ABIs after repository formatting. Both compiled module formats include finishadv and preserve upstream last_paid_round.
• Actual Tools consumers resolve the paired source SDK/models; capability and binary round-trip probes passed. npm SDK 1.0.103 lacks these new declarations, so publication remains a separate milestone.
• Current-head CI: run 39837092448 (passed).
• Coordinated candidate E2E: run 39837666494 passed all 14 flows, including operator termination and collateral withdrawal. Build reports confirm all four PR heads and Tools consumption of the paired Libraries checkout.

Companion PRs

• SYSIO #603: owns the continuation ABI; land the producer before releasing these declarations.
• Ethereum #198: enforces immediate roster revocation and next-epoch majority admission through whole-envelope continuation.
• Tools #97: exercises rotation and withdrawal using the coordinated candidate. Consumers requiring the new SDK interface need its published release or an explicitly validated candidate.