refactor: carry notice severity on RuntimeNotice; delete shallow event re-export

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code

[Tryanks]

Architecture round, candidate C2 (notice severity at the producing seam).

Problem — RuntimeNotice carried no severity; the UI presenter matched variants to guess Warning vs Success. Two PRs this week (#246, #259) edited that same match and collided (duplicate enum variant + rebase conflict), and the presenter test re-stated the rule in its own exhaustive match. Separately, crates/runtime/src/event.rs was a 17-line re-export module — shallow by the deletion test.

Change

• RuntimeNotice::severity() -> NoticeSeverity { Success, Warning } in the protocol, exhaustive match with no wildcard arm — adding a notice variant is a compile error until the author classifies it. No serialized fields added; zero wire impact.
• The UI presenter maps notice.severity() and keeps only localization + rendering; its test now checks representative examples instead of mirroring every variant.
• crates/runtime/src/event.rs deleted; HostEvent moved beside HostCx in host.rs; imports updated.

Wins — locality: new notices never touch the presenter; the cross-PR conflict class disappears; one shallow module deleted outright.

Behavior unchanged: same notices render with the same severities.

Gates: fmt / clippy -D warnings / full workspace tests — green locally.

🤖 Generated with Claude Code