[GH-ISSUE #19] Harden Hopper automation lifecycle, diagnostics, and headless ergonomics #16

Closed
opened 2026-10-15 18:19:58 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/19

Motivation

  • Launcher stdout does not reliably relay Python progress or exceptions.
  • Scripts depend on Hopper globals such as Document, complicating standalone tests and typing.
  • Exhaustive extraction is incomplete unless background analysis is awaited.
  • GUI activation and document loading complicate CI.
  • Demo sessions cannot save/export and are time-limited.

Scope

Use the authenticated socket for progress/diagnostics/results; add sanitized exception events; ship typed Hopper API stubs/facade; require analysis completion for exhaustive operations; expose lifecycle state; document demo/licensed differences; test bridge domain logic without import-time Hopper globals.

Acceptance criteria

  • Python exceptions reach callers as structured diagnostics.
  • Exhaustive tools cannot silently run during analysis.
  • Bridge logic has standalone facade tests.
  • CI reports clear UI/license/lifecycle remediation.
Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/19 ## Motivation - Launcher stdout does not reliably relay Python progress or exceptions. - Scripts depend on Hopper globals such as `Document`, complicating standalone tests and typing. - Exhaustive extraction is incomplete unless background analysis is awaited. - GUI activation and document loading complicate CI. - Demo sessions cannot save/export and are time-limited. ## Scope Use the authenticated socket for progress/diagnostics/results; add sanitized exception events; ship typed Hopper API stubs/facade; require analysis completion for exhaustive operations; expose lifecycle state; document demo/licensed differences; test bridge domain logic without import-time Hopper globals. ## Acceptance criteria - Python exceptions reach callers as structured diagnostics. - Exhaustive tools cannot silently run during analysis. - Bridge logic has standalone facade tests. - CI reports clear UI/license/lifecycle remediation.
Author
Owner

@morluto commented on GitHub (Jul 17, 2026):

Current main has structured bridge exception diagnostics and bounded analysis/lifecycle checks. Remaining work is the typed Hopper facade and standalone facade tests, bridge progress events, and verified demo/license/CI remediation. This remains an active hardening issue, not a missing basic lifecycle implementation.

<!-- gh-comment-id:5001696684 --> @morluto commented on GitHub (Jul 17, 2026): Current main has structured bridge exception diagnostics and bounded analysis/lifecycle checks. Remaining work is the typed Hopper facade and standalone facade tests, bridge progress events, and verified demo/license/CI remediation. This remains an active hardening issue, not a missing basic lifecycle implementation.
Author
Owner

@morluto commented on GitHub (Jul 20, 2026):

Split into focused child issues:

These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

<!-- gh-comment-id:5023442818 --> @morluto commented on GitHub (Jul 20, 2026): Split into focused child issues: - [ ] #350 - [ ] #351 These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#16
No description provided.