Recent sessions via session_search no-query: Substack parsing/timestamps, Vesta roadmap/module correction, and incomplete cost question.
Targeted searches: Substack OR parsing OR timestamps, roadmap OR operational learning OR learning, and cost OR coscostt OR pricing OR cron.
Checked cron overview with hermes cron list --all; inspected persisted delivery fields for the one ambiguous bare-telegram job.
Loaded relevant skills: hermes-agent and vesta-feature-development.
Durable Learnings Saved
None. One durable Vesta roadmap fact was identified, but the memory tool was unavailable in this cron environment, so no memory was written.
No skill changes: the Vesta feature skill already contains the key raw-email reprocessing lesson: dry-run is not success; apply, verify applied rows, then final clean dry-run.
Patterns Noticed
Vesta remains the dominant recurring workstream: email ingestion, Substack parsing, EPUB/reader UX, and modular roadmap design.
Moz corrected a context drift: “learn from mistakes” in the roadmap thread meant Vesta modules, not an operational repair ledger.
The most important production-repair standard is now clear: parser/reprocessor work is only done after applied-row logs plus follow-up zero-candidate verification.
Cost questions can be ambiguous between Hermes job cost and external product pricing; recent correction showed the need to identify the referenced product before local cron-cost analysis.
PWA/local cache state remains a recurring source of user-visible mismatch after server-side Vesta fixes.
Automation / Cron Hygiene
No active cron jobs showed errors in the CLI listing.
Recommendation: consider changing P Morning Audio Briefing from bare deliver: telegram to an explicit delivery target if Moz wants it in a specific chat/topic. Persisted origin currently resolves to Telegram DM P, so this is not an urgent breakage.
The Nightly Dream Log correctly delivers locally; no delivery-message side effects were attempted.
Candidate Next Actions for Moz
Decide whether the Vesta modular roadmap should be turned into a concrete design plan for Inbox/Triage/Wiki Export boundaries.
If Morning Audio should land in a group/topic rather than DM, reroute it explicitly instead of relying on deliver: telegram origin resolution.
For future ambiguous cost/product questions, include the product name or link when possible; the agent should still clarify from context when it can.
Confidence / Guardrails
High confidence on session-derived patterns; no destructive operations performed.
Memory write was attempted once and failed because memory was unavailable; I did not try alternate storage hacks.
I intentionally avoided editing cron jobs or skills because no low-risk unambiguous fix was required.