Telegram weekly summary reflects actual Weekly Intelligence state #18

New issue

Closed

opened 2026-05-28 18:14:53 +01:00 by bingoss · 1 comment

bingoss commented

2026-05-28 18:14:53 +01:00

Owner

What to build

Type: AFK.

Add the weekly Telegram summary through Hermes using actual Weekly Intelligence state. The message should summarize active/staged outcome, stage statuses, key blockers, generated plan/queue counts, and artifact links.

Acceptance criteria

Weekly summary sends through Hermes only after the Weekly Intelligence state is written.
Message content is derived from Postgres state and artifact links, not local guesses or stale markdown.
Missing Telegram configuration records safe diagnostics without breaking unrelated product state.
Tests are written first for sent, skipped-unconfigured, and failed-safe paths.

Blocked by

## What to build Type: AFK. Add the weekly Telegram summary through Hermes using actual Weekly Intelligence state. The message should summarize active/staged outcome, stage statuses, key blockers, generated plan/queue counts, and artifact links. ## Acceptance criteria - [ ] Weekly summary sends through Hermes only after the Weekly Intelligence state is written. - [ ] Message content is derived from Postgres state and artifact links, not local guesses or stale markdown. - [ ] Missing Telegram configuration records safe diagnostics without breaking unrelated product state. - [ ] Tests are written first for sent, skipped-unconfigured, and failed-safe paths. ## Blocked by - #17

bingoss commented

2026-05-29 08:25:45 +01:00

Author

Owner

Issue #18 completion audit

Implemented and verified:

Added a Postgres-derived Weekly Intelligence Telegram summary worker that sends through an injected Hermes Telegram sender only after the weekly run is terminal and stage state is written.
Message content is built from Postgres run state, stage statuses, produced counts, key blockers, and artifact links; raw diagnostics, payloads, artifact bodies, and stale markdown are not used.
Missing Telegram config records a skipped optional weekly_summary_notification stage and safe diagnostics without changing run status or active/staged promotion state.
Hermes sender failures record a failed optional weekly_summary_notification stage with safe diagnostics and do not alter unrelated product state.
Growth Orchestrator now runs weekly_summary_notification after promotion, so summaries can reflect active completed state.

Acceptance criteria audit:

Weekly summary sends through Hermes only after Weekly Intelligence state is written: met by terminal-state guard and orchestrator post-promotion test.
Message content is derived from Postgres state and artifact links: met by direct Postgres state query and tests asserting counts/stages/links while excluding raw markers.
Missing Telegram configuration records safe diagnostics without breaking unrelated product state: met by skipped-unconfigured test preserving completed active run state.
Tests first for sent, skipped-unconfigured, and failed-safe paths: met; server RED failed on missing function before implementation, then GREEN.

Tests run on codex-server:

python3 -m unittest tests.test_weekly_telegram_summary tests.test_growth_orchestrator_worker tests.test_content_planner_contract tests.test_postgres_dashboard tests.test_postgres_schema tests.test_business_profile_worker tests.test_keyword_competitor_worker tests.test_visibility_worker tests.test_public_listening_worker tests.test_authority_research_worker tests.test_technical_audit_worker
git diff --check
Result: 170 tests passed; diff check clean.

Issue #18 completion audit Implemented and verified: - Added a Postgres-derived Weekly Intelligence Telegram summary worker that sends through an injected Hermes Telegram sender only after the weekly run is terminal and stage state is written. - Message content is built from Postgres run state, stage statuses, produced counts, key blockers, and artifact links; raw diagnostics, payloads, artifact bodies, and stale markdown are not used. - Missing Telegram config records a skipped optional weekly_summary_notification stage and safe diagnostics without changing run status or active/staged promotion state. - Hermes sender failures record a failed optional weekly_summary_notification stage with safe diagnostics and do not alter unrelated product state. - Growth Orchestrator now runs weekly_summary_notification after promotion, so summaries can reflect active completed state. Acceptance criteria audit: - Weekly summary sends through Hermes only after Weekly Intelligence state is written: met by terminal-state guard and orchestrator post-promotion test. - Message content is derived from Postgres state and artifact links: met by direct Postgres state query and tests asserting counts/stages/links while excluding raw markers. - Missing Telegram configuration records safe diagnostics without breaking unrelated product state: met by skipped-unconfigured test preserving completed active run state. - Tests first for sent, skipped-unconfigured, and failed-safe paths: met; server RED failed on missing function before implementation, then GREEN. Tests run on codex-server: - python3 -m unittest tests.test_weekly_telegram_summary tests.test_growth_orchestrator_worker tests.test_content_planner_contract tests.test_postgres_dashboard tests.test_postgres_schema tests.test_business_profile_worker tests.test_keyword_competitor_worker tests.test_visibility_worker tests.test_public_listening_worker tests.test_authority_research_worker tests.test_technical_audit_worker - git diff --check - Result: 170 tests passed; diff check clean.

bingoss closed this issue

2026-05-29 08:25:45 +01:00

Commenting is not possible because the repository is archived.

No labels

codex-token-write-test-1780004082

No milestone

No project

No assignees

1 participant

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

bingoss/owned-growth-engine#18

No description provided.

Rows
Columns