Repository navigation
feat: make required actions visible in every completed cycle - #322
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
There was a problem hiding this comment.
ℹ️ No critical issues — one minor suggestion inline.
Reviewed changes
Initial review of the clarify-operator-actions implementation and archive: required-action registration, the consolidated notification, cycle/account evidence, cash evidence and log stream routing.
- Required-action registry —
outcome.record_actionstores fixed reason codes with private scope keys, deduplicated per event and reason.action_summaryexposes only codes, counts and fixed instructions externally. - Notifications in every mode —
_finalize_notificationdrops thedry_run_requested()silence. Recorded actions, token expiry and a forced TZ preview now notify in simulation too, andNotification resultis logged explicitly. - Action sources — dividend rejections are mapped through
DIVIDEND_REJECTION_ACTIONS, which covers everyreject(...)string insync.pyand has an AST completeness test. Trade, mapping, review, corporate-action and diagnostic findings are also recorded. Selection, writes and exit codes are unchanged. - Cycle and account evidence —
log_operational_resultreports success, success with user action required or failure, plus per-account imports, duplicates, holds, deferrals and cash. Unknown values are reported asunavailable. - Cash evidence in
ghost_update_cash_balance— the run now recordsnot updated,simulated,uncertain/failedorrequest reported successfulper account. The PR body already flags this shared-helper change for DEGIRO propagation. - Log streams —
__main__sends DEBUG/INFO to stdout and WARNING+ to stderr.entrypoint.shruns Supercronic v0.2.51 with-passthrough-logs -split-logs, and the container runtime check verifies both streams.
claude-opus-5-5 | 𝕏
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Since the last Pullfrog review, one commit landed. It fixes the earlier finding about the notification label.
- Action-only notification label —
_finalize_notificationnow uses"Token expiry"only whendays is not Noneand otherwise falls back to"User action". The label now follows the same branch order as the title/body selection, so private delivery logs name the real trigger. - Delivery matrix test —
test_operator_action_delivery_explicitnow checks that"Token expiry notification"never appears and that"User action notification"is logged when delivery is configured.
claude-opus-5-5 | 𝕏

Behavior
Pending review holds and other required actions could survive a successful cycle without a reminder. Register explicit required-action decisions and send one redacted consolidated summary per completed cycle, including simulation, until current evidence resolves them. Keep financial requests, selection, approvals and exits unchanged.
Report notification delivery and per-account import/cash evidence separately. Preserve native application levels under Supercronic: DEBUG/INFO on stdout, WARNING+ on stderr. Label APP_VERSION as build identity. Synchronize and archive the approved clarify-operator-actions specification.
Release impact
Minor: successful cycles with required actions now notify in simulation and live mode. Clean success sends no heartbeat. No financial migration. Rollback: revert the change. Stable publication and deployment remain separate. Shared-helper propagation: cash acceptance evidence in ghostfolio.py changed; DEGIRO remains pinned under ADR 0007 and needs a separate propagation change.
Verification
AI assistance
Codex implemented and checked the change. Local review covered repository standards, approved scenarios, credential boundaries and the semantic diff. CI and Pullfrog must verify the published head.
Pullfrog review
Pullfrog is the sole reviewer. Require a completed review of the final head and resolve actionable threads. All technical CI checks remain required; ignore only the known sticky pullfrog-approval status. Run pr-ship under the repository workflow.
Review evidence: completed Pullfrog review of
f7c816274e33b331778fe65791e9332a7d733e9a. The actionable thread is resolved. All required CI checks pass; pr-ship merged the evaluated head as18b6ece4769ccb928c624c15c1f32ceedcb79a51.