Finalize run metadata and normalize every invocation outcome

[codeforester]

Parent: #50

Train position: 2 of 22
Phase: P0 — Trustworthy lifecycle

Problem

Core-owned run.json can remain in running forever, and success, usage errors, interrupts, and unexpected failures do not share one terminal outcome model.

Acceptance criteria

• Owned run.json transitions from running to a terminal state with exit code, end time, and duration for success, usage error, abort/Ctrl+C, and unexpected failure.
• Generic and custom profiles follow one core-owned outcome model; history persistence is not responsible for metadata finalization.
• Known outcomes map to documented messages and exit codes; unexpected errors are clean by default and retain traceback detail under an explicit debug/log policy.
• Finalization failures preserve the primary outcome, and completed in-process runs do not remain running.
• Context construction and partial runtime setup are transactional or have explicit rollback behavior.

Dependencies

• Make lifecycle teardown failure-safe #51