Ark Error Manager public beta tested the complete path of an application error
The 0.1.0-dev series connected ordered processing, classification, policy, reporting, presentation, recovery, sanitization, and Flutter hooks.
Capturing an error does not define its policy
The public beta of ark_error_manager and ark_error_manager_flutter introduced an application-owned ordered pipeline for occurrence, classification, policy, reporting, presentation, recovery, and observation. It also added isolated pipeline-failure handling, strict report sanitization, root-Zone callbacks, child-isolate binding, and Flutter framework and platform hooks.
The beta tested ownership at the system boundary. A single binding installed the Flutter handlers, preserved previous callbacks, and restored them on close. Navigation presentation remained an adapter rather than a reason to inject the manager into each feature. The package supplied mechanisms; product decisions about messages, retry, or recovery remained outside it.
The prereleases remain in the pub.dev version history. Current integrations should use 1.0.0.