coilyco-flight-deck/ward

Watch

Remove the provider-specific panic reporter from Ward core #1648

New issue

Closed

opened 2026-08-05 10:09:17 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-05 10:09:17 +00:00

Member

Outcome

Remove the provider-specific panic reporter SDK and environment-based exporter from Ward core. Panics remain visible through normal local failure, lifecycle, and logging surfaces.

Scope

Delete errorreport.go, its tests and documentation, reporter initialization and recovery wiring, the provider SDK dependency, and the WARD_SENTRY environment surface.
Preserve normal panic behavior, nonzero failure, stderr, and local run evidence.
Do not add another in-process network crash reporter.

Preserved boundary

External collectors may consume Ward records out of process.
Lifecycle semantics from #1618 and secret-safe artifact requirements from #1582 remain authoritative.

Acceptance

Ward core has no network crash-reporter SDK or provider-specific reporter environment variables.
Top-level panics still fail loudly and leave supported local evidence.
Documentation describes only Ward-owned local behavior.

Coordinates with #1618 and #1582. Blocks documentation consolidation in #1624.

## Outcome Remove the provider-specific panic reporter SDK and environment-based exporter from Ward core. Panics remain visible through normal local failure, lifecycle, and logging surfaces. ## Scope * Delete `errorreport.go`, its tests and documentation, reporter initialization and recovery wiring, the provider SDK dependency, and the `WARD_SENTRY` environment surface. * Preserve normal panic behavior, nonzero failure, stderr, and local run evidence. * Do not add another in-process network crash reporter. ## Preserved boundary * External collectors may consume Ward records out of process. * Lifecycle semantics from #1618 and secret-safe artifact requirements from #1582 remain authoritative. ## Acceptance * Ward core has no network crash-reporter SDK or provider-specific reporter environment variables. * Top-level panics still fail loudly and leave supported local evidence. * Documentation describes only Ward-owned local behavior. Coordinates with #1618 and #1582. Blocks documentation consolidation in #1624.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-05 10:09:17 +00:00

coilyco-ops referenced this issue

2026-08-05 10:09:42 +00:00

Collapse the documentation tree into durable product contracts #1624

coilyco-ops commented

2026-08-05 10:59:29 +00:00

Author

Member

Settled implementation contract

Hard-delete errorreport.go, its tests, Sentry initialization and top-level recovery wiring, the sentry-go dependency, WARD_SENTRY_DSN, WARD_SENTRY_ENVIRONMENT, and docs/error-reporting.md plus its index link.
Unrecovered top-level panics use native Go behavior: stack trace to stderr and a nonzero process exit.
Add no crash file, schema, telemetry hook, compatibility warning, local reporter, or replacement network exporter.
Keep the existing broker request-handler and launch-worker panic recovery. Those paths are lifecycle containment, not telemetry, and continue to emit the #1618 failure state and #1582-redacted persisted evidence.
Existing supported log paths may capture panic output normally. Ward must not create a special raw panic archive.
Ignore legacy WARD_SENTRY values silently. Ward does not migrate or delete external secrets or operator configuration.
No deployment-side injection or cross-repository consumer was found in the current checkout inventory, so this issue needs no companion cleanup issue.

Priority is P2 because this blocks #1624.

## Settled implementation contract * Hard-delete errorreport.go, its tests, Sentry initialization and top-level recovery wiring, the sentry-go dependency, WARD_SENTRY_DSN, WARD_SENTRY_ENVIRONMENT, and docs/error-reporting.md plus its index link. * Unrecovered top-level panics use native Go behavior: stack trace to stderr and a nonzero process exit. * Add no crash file, schema, telemetry hook, compatibility warning, local reporter, or replacement network exporter. * Keep the existing broker request-handler and launch-worker panic recovery. Those paths are lifecycle containment, not telemetry, and continue to emit the #1618 failure state and #1582-redacted persisted evidence. * Existing supported log paths may capture panic output normally. Ward must not create a special raw panic archive. * Ignore legacy WARD_SENTRY values silently. Ward does not migrate or delete external secrets or operator configuration. * No deployment-side injection or cross-repository consumer was found in the current checkout inventory, so this issue needs no companion cleanup issue. Priority is P2 because this blocks #1624.

coilyco-ops referenced this issue from a commit

2026-08-05 20:46:14 +00:00

refactor: remove the panic reporter

coilyco-ops closed this issue

2026-08-05 20:46:14 +00:00

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

coilyco-flight-deck/ward#1648

No description provided.

Rows
Columns