Skip to content

Commit b4ccea2

Browse files
committed
Logged the container matrix shakedown
1 parent dd60300 commit b4ccea2

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

ACTIVITY.log.jsonl

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,3 +52,4 @@
5252
{"who": "AGENT", "what": "Documented the RUN_TIDY escape hatch", "where": ["Makefile", "CONTRIBUTING.md"], "when": "2025-10-23T23:06:16Z", "why": "Reviewers wanted the skip flag explained in both the Makefile and contributor docs", "how": "Added a comment above host-tidy and dropped a matching bullet in CONTRIBUTING", "protip": "If you give folks an escape hatch, spell out when to flip it back"}
5353
{"who": "AGENT", "what": "Split the log helper into a reusable script", "where": ["Makefile", "tools/log_activity_dispatch.sh", "AGENTS.md"], "when": "2025-10-23T23:07:58Z", "why": "Review demanded the Makefile recipe shrink and centralize validation", "how": "Added tools/log_activity_dispatch.sh, pointed the log target at it, and warned agents in AGENTS.md", "protip": "Keep the logging interface single-source; shell snippets rot faster than scripts"}
5454
{"who": "AGENT", "what": "Tweaked the activity schema regex after ajv balked", "where": ["ACTIVITY.schema.json"], "when": "2025-10-23T23:10:23Z", "why": "The stricter uri format broke validation, so I stuck with a hardened regex", "how": "Dropped the draft-format flag and kept the host/path matcher that still screens bogus schemes", "protip": "AJV's builtin formats lag behind—lean on regex if you need deterministic CI behavior"}
55+
{"who": "AGENT", "what": "Replayed the CI matrix locally", "where": ["Makefile", "tools/container/dispatch.sh", "ACTIVITY.schema.json"], "when": "2025-10-23T23:11:53Z", "why": "Needed to prove the containerized builds/tests still succeed after the shell and schema tweaks", "how": "Ran make both, make test-both, make lint, and make activity-validate; addressed an ajv format complaint along the way", "protip": "Run the same docker harness CI uses—dry runs hide drift"}

0 commit comments

Comments
 (0)