🦛 Hippo Memory Insights — 2026-05-05

[github-actions[bot]]

Summary

• Memories in store: 525 (473 episodic, 52 semantic)
• New lessons learned from commits today: 0 (no fix/revert/bug commits in last 7 days)
• Consolidation: 125 episodic merged, 52 new semantic memories, 25 duplicates deduped
• Highest-confidence memories: Verified incidents around stale .lock.yml files, missing node runtime, and Codex auth failures

Top Memories Surfaced

1. [score=1.00, verified] Stale workflow .lock.yml files cause churn and CI friction — run make recompile after markdown workflow edits.
2. [score=1.00, verified] Codex auth failures can break agent jobs — verify auth/mode/token setup before reruns.
3. [score=1.00, verified] node: command not found on GPU/self-hosted paths when node runtime/tooling is missing — validate runtimes and PATH early.
4. [score=1.00] CI validate-yaml job scans all YAML files for ANSI escape sequences before other jobs run.
5. [score=0.98] Unformatted code causes immediate CI failures — make fmt is mandatory before commit/PR.
6. [score=0.96] make build && make fmt after first significant code change catches compile errors and formatting issues early.
7. [score=0.95] Validation refactoring guide at scratchpad/validation-refactoring.md — step-by-step examples available.

Suggested Improvements

Error Patterns

• Stale .lock.yml files are the most-recalled incident. Add a make check-stale target or a pre-commit hook that warns when .lock.yml files are out of sync with their source .md workflows. File: any *.lock.yml under .github/aw/.
• Node runtime missing on self-hosted runners: Add an early PATH/runtime validation step at the top of any workflow that requires Node — fail fast with a clear message rather than a cryptic command not found.
• Codex auth failures: Document the exact setup checklist in the workflow health runbook (.github/aw/runbooks/workflow-health.md) and add a pre-flight check job.

Code Quality

• Type safety gaps: Memories consistently flag mixing JobName/StepID string types as a recurring bug vector. Enforce distinct string types via Go type aliases across pkg/workflow/.
• File organization: Multiple memories note "prefer many smaller files grouped by functionality" and "add new files for new features rather than extending existing ones." Consider auditing large files in pkg/ for splitting opportunities.
• Console formatting: Repeated pattern — plain fmt.Errorf used instead of console.FormatErrorMessage. A linter rule or grep CI check for this anti-pattern would eliminate recurrence.
• JavaScript refactoring: pkg/workflow/js/ files should be refactored into separate .cjs modules — see skills/javascript-refactoring/SKILL.md.

CI Health

• make test is >5 min — memories explicitly warn to avoid running locally. Confirm that the fast path (make test-unit, ~3s) is documented prominently in DEVGUIDE.md for new contributors.
• CI YAML ANSI check: The validate-yaml pre-flight is effective; ensure it runs as a required status check so it cannot be bypassed.
• Unformatted code as CI blocker: make fmt should be enforced by a pre-commit hook (beyond the CI gate) to reduce failed-run churn.

Quick Wins

1. Add pre-commit hook for make fmt — eliminates the most common CI failure; ~1 hour to implement.
2. Add make recompile reminder to workflow edit docs — addresses the top verified incident; ~15 min.
3. Grep CI check for fmt.Errorf without console.FormatErrorMessage — catches error-formatting anti-pattern at PR time; ~30 min.
4. Document make test-unit prominently in DEVGUIDE.md — reduces developer friction; ~15 min.
5. Early node/runtime validation step in agent workflows — eliminates cryptic self-hosted runner failures; ~1 hour.

Longer-term Themes

• Workflow lock file management is the single most-recalled incident cluster. A first-class solution (auto-regeneration, CI guard, or lock-free approach) would significantly reduce recurring toil.
• Codex/agent auth reliability appears multiple times — this suggests the auth/token refresh story needs a dedicated hardening effort.
• Type safety in workflow structs is flagged repeatedly across multiple sessions. A systematic audit and enforcement of Go type aliases for domain IDs (JobName, StepID, WorkflowName) would prevent a class of bugs.
• Console output discipline (stderr vs stdout, console.FormatErrorMessage) is noted in many memories. A lightweight linter or Makefile check would institutionalize the pattern.

Memory Health

Memory store details

• Total: 525 memories (473 episodic, 52 semantic)
• Verified: 3 | Observed: 470 | Inferred: 52
• At risk (<0.2 strength): 0
• Avg strength: 1.00
• 7 low-quality memories flagged by audit (run hippo audit for details — candidates for pruning)
• Last sleep: 2026-05-05T07:05Z
• Embeddings: 525/525 up to date

No stale memories detected. Pruning candidates: run mcpscripts hippo --args "audit" to review the 7 flagged low-quality entries.

References:

• §25362493917

Generated by Daily Hippo Learn · ● 560.1K · ◷

• expires on May 8, 2026, 7:08 AM UTC

[github-actions[bot]]

💥 KA-POW! The Smoke Test Agent has arrived!

🦸 WHOOSH! Agent Claude swooped through this dimension, fired up engines, and blazed through 19 smoke tests at WARP SPEED!

⚡ ZAP! BANG! BOOM! All systems nominal — the Claude engine is FULLY OPERATIONAL on Run §25362371516!

🌟 The hero has spoken — and the smoke test has PASSED! 🌟

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

• accounts.google.com
• android.clients.google.com
• clients2.google.com
• contentautofill.googleapis.com
• safebrowsingohttpgateway.googleapis.com
• www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "clients2.google.com"
    - "contentautofill.googleapis.com"
    - "safebrowsingohttpgateway.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• Bump AWF firewall version to v0.25.39 #30263 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

💥 [THE END] — Illustrated by Smoke Claude · ● 285K · ◷