Skip to content

revert(discord): drop opt-in raw-reaction journal (#129 DROP, t_d72c6944) - #1273

Merged
ang-fleet-lander[bot] merged 1 commit into
mainfrom
audit/gateway/revert-129
Sep 27, 2026
Merged

ang-fleet-lander[bot] merged 1 commit into
mainfrom
audit/gateway/revert-129

Conversation

@ang-fleet-workers

@ang-fleet-workers ang-fleet-workers Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

Card: t_d72c6944. This is a fork-PR audit DROP of #129, confirmed by Ace's ruling on 2026-09-27 00:39 PT. The disposition is recorded in FINAL.md (#1128).

It reverts the opt-in raw-reaction journal from the Discord adapter:

  • plugins/platforms/discord/adapter.py loses 133 lines.
  • tests/gateway/test_discord_reaction_journal.py is deleted.
  • Net change is 2 files, -349 lines.

Verification:

  • git grep finds no reaction_journal / DISCORD_REACTION_JOURNAL references outside the audit docs.
  • py_compile passes.
  • pytest tests/gateway/test_discord_connect.py tests/gateway/test_discord_reactions.py gives 19 passed and 1 failed. The failure is test_free_response_inline_other_bot_mention_reaches_platform_event, and it fails the same way on a clean origin/main 4511497.

Ops half, which Apollo applies at land time: remove discord.reaction_journal from ~/.hermes/config.yaml. Once this merges, that key has no reader.

Note: one manual reader of the existing reactions.jsonl file remains. It is greenhouse-tools seed_triage.py report --journal, for the verdict-age column. Ace ruled the DROP knowing this.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Fork-PR audit verdict DROP (lead t_03e35f0e, card t_d72c6944): the
journal is written but nothing in the fleet reads it on a schedule.
The live journal (~/.hermes/greenhouse/reactions.jsonl) is at seq
40486 on 2026-09-25, so the feature does fire. Its only reader is the
manual `seed_triage.py report --journal` in ANG-Ventures/greenhouse-tools
(verdict-age column). That tool is not scheduled, and there is no local
checkout of it on the Studio.

Reverts 56be472. The conflict in adapter.py was resolved by keeping
main's seeded_extra/_skip_env_bridge shape and removing the
reaction_journal keys.

Verified: tests/gateway/test_discord_connect.py plus
test_discord_reactions.py give 19 passed and 1 failed. The failure is
test_post_connect_initialization_retries_fingerprint_after_timeout, and
it fails the same way on fork/main 382fc62.
@ang-fleet-lander

Copy link
Copy Markdown

🤖 merged-by: apollo · lane: review · gate: ADVISORY (FleetReview not green for b492586): fleetreview-advisory-20260927-standing.md · why: Apollo read diff: pure revert of #129 (adapter -133, journal test deleted), 0 remaining reaction_journal refs; Ace ruled DROP 09-27 00:39 (t_d72c6944)

@ang-fleet-lander
ang-fleet-lander Bot added this pull request to the merge queue Sep 27, 2026
Merged via the queue into main with commit 68644a1 Sep 27, 2026
41 checks passed
@ang-fleet-lander
ang-fleet-lander Bot deleted the audit/gateway/revert-129 branch September 27, 2026 08:23
@ang-fleet-ci-actuators ang-fleet-ci-actuators Bot added the fleetreview:post-merge Ask FleetReview to review this MERGED pull (merge commit vs first parent) label Sep 27, 2026
@ang-prism

ang-prism Bot commented Sep 27, 2026

Copy link
Copy Markdown

FleetReview

Post-merge review (fleetreview:post-merge override): this reviewed the merge commit against its first parent — the bytes that already shipped. It is not a pre-merge gate pass.

Reviewed with 2 of 3 model families — anthropic unavailable.

Confidence: 2/5

Findings

  • P1 plugins/platforms/discord/adapter.py:1857 — Journal Disabled

FleetReview provenance · models: B=gpt-6-sol, C=claude-code-opus-5-5, D=grok-4.6, F=gpt-6-sol · cost: $0.51 · duration: 2m 50s · rounds: 2 · files examined: 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fleetreview:post-merge Ask FleetReview to review this MERGED pull (merge commit vs first parent)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant