Merge branch 'feat/data-layer-monitor' into feat/data-flywheel-trainer

# Conflicts:
#	.agent/AGENTS.md
#	.agent/skills/_index.md
#	.agent/skills/_manifest.jsonl
#	.gitignore
#	README.md
#	docs/architecture.md

Author: codejunkie99

.agent/AGENTS.md

@@ -41,6 +41,19 @@ are the exact failure mode this layer prevents.
 - Load a full `SKILL.md` only when its triggers match the current task
 - Every skill has a self-rewrite hook; invoke it after failures
 
+## Design Systems
+- If the project root contains `DESIGN.md`, treat it as the source of truth
+  for visual design decisions and load `skills/design-md/SKILL.md` when a
+  task mentions `DESIGN.md`, Google Stitch, design tokens, design system,
+  or visual design. (The skill's `preconditions` field gates loading on
+  `DESIGN.md` actually existing — keep this rule in lockstep with
+  `skills/_manifest.jsonl` to avoid same-task / different-harness drift.)
+- Prefer exact tokens, component rules, and design rationale from
+  `DESIGN.md` over invented colors, typography, spacing, shadows, or motion.
+- Do not modify `DESIGN.md` unless the user explicitly asks for a design
+  system change; implementation work consumes the contract, it doesn't
+  edit it.
+
 ## Protocols
 - `protocols/permissions.md` — read before any tool call
 - `protocols/tool_schemas/` — typed interfaces for external tools
@@ -55,6 +68,9 @@ Daily driver, highest-leverage first:
   in one shot (stage + graduate + render). For rules you already know.
 - `show.py` — one-screen dashboard of brain state: episodes, candidates,
   lessons, failing skills, activity graph.
+- `data_layer_export.py` — local cross-harness activity/data-layer export:
+  agent events, cron timelines, tokens/cost estimates, categories,
+  harness mix, `dashboard.html`, and `daily-report.md`.
 - `data_flywheel_export.py` — local export of approved, redacted runs into
   trace records, context cards, eval cases, training-ready JSONL, and
   flywheel metrics. It does not train models or call APIs.

.agent/memory/semantic/DECISIONS.md

@@ -14,3 +14,9 @@
 **Rationale:** Each layer has different retention and retrieval needs. Flat memory breaks at ~6 weeks.
 **Alternatives considered:** Flat directory (fails at scale), vector store (over-engineered for single user).
 **Status:** active
+
+## 2026-04-26: Add `design-md` seed skill (DESIGN.md / Google Stitch)
+**Decision:** Ship a sixth seed skill, `design-md`, that points coding agents at a root `DESIGN.md` (Google Stitch format) as the visual-system source of truth. Loads only when `DESIGN.md` exists at the project root, default behavior is read-only on the contract file, and validation prefers `npx @google/design.md lint DESIGN.md` over hand-checks.
+**Rationale:** `DESIGN.md` is becoming a de facto contract for AI-driven UI work; without an explicit skill, agents invent ad-hoc tokens that drift from the user's design system. Gating on `DESIGN.md`-existence keeps the skill silent on projects that don't use the format.
+**Alternatives considered:** Bundle the rules into `git-proxy` or `skillforge` (wrong scope, wrong triggers); leave it to per-project `.agent/skills/` overrides (loses the cross-harness benefit); broader triggers like "UI"/"frontend"/"components"/"styling" (too generic, loads on every UI task even without DESIGN.md).
+**Status:** active

.agent/skills/_index.md

@@ -27,10 +27,29 @@ Triggers: "deploy", "ship", "release", "go live"
 Constraints: all tests passing, no unresolved TODOs in diff,
 requires human approval for production.
 
+## data-layer
+Cross-harness activity monitoring and dashboard exports.
+Triggers: "data layer", "dashboard", "agent analytics", "resource usage",
+"cron monitoring", "daily report", "tokens"
+Constraints: local-only by default; no screenshot delivery without explicit user
+approval; do not commit private `.agent/data-layer/` exports.
+
 ## data-flywheel
 Turns approved, redacted runs into reusable local artifacts: trace records,
 context cards, eval cases, training-ready JSONL, and flywheel metrics.
 Triggers: "data flywheel", "trace to train", "training traces",
 "context cards", "eval cases", "approved runs", "vertical intelligence"
 Constraints: local-only by default; human-approved runs only; redaction required
 before trainable; does not train models.
+
+## design-md
+Uses a root `DESIGN.md` as the portable visual system contract for
+Google Stitch workflows. Loads only when `DESIGN.md` exists at the
+project root.
+Triggers: "DESIGN.md", "design.md", "Google Stitch", "design tokens",
+"design system", "visual design"
+Preconditions: DESIGN.md exists at project root.
+Constraints: prefer DESIGN.md tokens over invented values, do not modify
+DESIGN.md unless the user explicitly asks, preserve unknown sections when
+an edit IS authorised, validate with `npx @google/design.md lint DESIGN.md`
+when available.

.agent/skills/_manifest.jsonl

@@ -3,4 +3,6 @@
 {"name":"git-proxy","version":"2026-01-01","triggers":["commit","push","branch","merge","rebase","pull request","PR"],"tools":["bash"],"preconditions":[".git exists"],"constraints":["never force push to main","never force push to protected branches","run tests before push"],"category":"operations"}
 {"name":"debug-investigator","version":"2026-01-01","triggers":["debug","why is this failing","investigate","stack trace","bug"],"tools":["bash","memory_reflect"],"preconditions":[],"constraints":["reproduce before fixing","fix root cause, not symptoms"],"category":"engineering"}
 {"name":"deploy-checklist","version":"2026-01-01","triggers":["deploy","ship","release","go live"],"tools":["bash"],"preconditions":[],"constraints":["all tests passing","no unresolved TODOs in diff","requires human approval for production"],"category":"operations"}
+{"name":"data-layer","version":"2026-04-25","triggers":["data layer","dashboard","agent analytics","resource usage","cron monitoring","daily report","tokens"],"tools":["bash","git"],"preconditions":[".agent exists"],"constraints":["local-only by default","no screenshot delivery without explicit user approval","do not commit private .agent/data-layer exports"],"category":"operations"}
 {"name":"data-flywheel","version":"2026-04-25","triggers":["data flywheel","trace to train","training traces","context cards","eval cases","approved runs","vertical intelligence"],"tools":["bash","git"],"preconditions":[".agent exists"],"constraints":["local-only by default","human-approved runs only","redaction required before trainable","do not train models"],"category":"operations"}
+{"name":"design-md","version":"2026-04-26","triggers":["DESIGN.md","design.md","Google Stitch","Stitch","design tokens","design system","visual design"],"tools":["bash","memory_reflect"],"preconditions":["DESIGN.md exists at project root"],"constraints":["prefer DESIGN.md tokens over invented values","do not modify DESIGN.md unless the user explicitly asks","preserve unknown sections when an edit IS authorised","validate when tooling is available"],"category":"design"}

.agent/skills/data-layer/SKILL.md

@@ -0,0 +1,120 @@
+---
+name: data-layer
+version: 2026-04-25
+triggers: ["data layer", "dashboard", "agent analytics", "resource usage", "cron monitoring", "daily report", "tokens"]
+tools: [bash, git]
+preconditions: [".agent exists"]
+constraints: ["local-only by default", "do not send screenshots without explicit user approval", "do not commit private .agent/data-layer exports"]
+---
+
+# Data Layer - cross-harness monitoring for the portable brain
+
+Use this skill when the user wants to measure agent activity across Claude Code,
+Hermes, OpenClaw, Codex, Cursor, OpenCode, Windsurf, Pi, Antigravity, or any
+custom loop using `.agent/`.
+
+The goal is local business intelligence for the whole agent suite:
+
+- what harnesses are active
+- how many agent events are happening
+- when cron/scheduled agents fire
+- which crons started/finished and how long they ran
+- how many agents are active
+- tokens and estimated cost by hour/day/week/month
+- resource usage by user-defined category
+- workflow success/error rates
+- KPI summary rows for cron cadence, run volume, reliability, active agents,
+  workflow breadth, token usage, and estimated cost
+- screenshot-ready daily resource reports
+
+## Hard Rules
+
+- Stay local-first. Do not add telemetry or remote sync.
+- Do not store raw prompts, raw code, client names, emails, phone numbers, or
+  unredacted business records in shared examples.
+- Do not commit `.agent/data-layer/` exports unless the user explicitly reviewed
+  and sanitized them.
+- Do not send dashboard screenshots to email, Slack, webhooks, or any other
+  channel unless the user explicitly approves the destination.
+
+## Inputs
+
+Default inputs:
+
+```text
+.agent/memory/episodic/AGENT_LEARNINGS.jsonl
+.agent/data-layer/harness-events.jsonl     optional
+.agent/data-layer/cron-runs.jsonl          optional
+.agent/data-layer/category-rules.json      optional
+```
+
+`AGENT_LEARNINGS.jsonl` is the shared activity log. Optional files let users add
+events from harnesses that do not automatically write rich events yet.
+
+## Export
+
+Run:
+
+```bash
+python3 .agent/tools/data_layer_export.py --window 30d --bucket day
+```
+
+Use `--bucket hour`, `--bucket day`, `--bucket week`, or `--bucket month` for
+different chart grains.
+
+Outputs go to:
+
+```text
+.agent/data-layer/exports/<YYYY-MM-DD>/
+```
+
+Key outputs:
+
+- `agent-events.jsonl/csv`
+- `cron-runs.jsonl/csv`
+- `cron-timeline.json/csv`
+- `activity-series.json/csv`
+- `category-summary.json/csv`
+- `harness-summary.json/csv`
+- `workflow-summary.json/csv`
+- `kpi-summary.json/csv`
+- `dashboard-summary.json`
+- `dashboard-report.json`
+- `dashboard.html`
+- `daily-report.md`
+
+## Categories
+
+Users can define any categories they want in
+`.agent/data-layer/category-rules.json`, for example:
+
+```json
+{
+  "default_category": "uncategorized",
+  "rules": [
+    {"category": "coding", "skills": ["debug-investigator", "git-proxy"]},
+    {"category": "admin", "run_types": ["cron"]},
+    {"category": "financial", "workflows": ["invoice_collection"]},
+    {"category": "personal", "workflows": ["calendar_coordination"]},
+    {"category": "work", "phases": ["plan", "review", "qa", "ship"]}
+  ]
+}
+```
+
+## Daily Screenshot Report
+
+For daily resource management:
+
+1. Run the exporter from a user-approved cron or scheduled agent.
+2. Open `dashboard.html`.
+3. Capture the Resource Overview, Activity, Tokens, Cron Runs, Task Categories,
+   Harness Mix, Workflow Outcomes, Cron Gantt, and Cron Timeline sections.
+4. Send the screenshot only through an explicitly approved channel.
+
+The exporter creates `daily-report.md` as the text summary. It does not send
+anything by itself.
+
+## Self-rewrite hook
+
+If exports are confusing twice in a row, improve category rules, schema names,
+or dashboard labels before adding heavier dashboard dependencies.

.agent/skills/design-md/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: design-md
+version: 2026-04-26
+triggers: ["DESIGN.md", "design.md", "Google Stitch", "Stitch", "design tokens", "design system", "visual design"]
+tools: [bash, memory_reflect]
+preconditions: ["DESIGN.md exists at project root"]
+constraints: ["prefer DESIGN.md tokens over invented values", "do not modify DESIGN.md unless the user explicitly asks", "preserve unknown sections when an edit IS authorised", "validate when tooling is available"]
+---
+
+# DESIGN.md — portable visual system contract
+
+Use this skill when a task touches Google Stitch's `DESIGN.md` format or
+the project explicitly references its design system / design tokens. The
+skill loads only when `DESIGN.md` exists at the project root (see
+`preconditions` above), so general UI / frontend / component work that
+isn't tied to a `DESIGN.md` won't trip it.
+
+## Source of truth
+- `DESIGN.md` is a contract file. Read it before changing visual UI.
+- Treat YAML front matter tokens as normative values: colors, typography,
+  spacing, radius, and component tokens are exact inputs to code.
+- Treat the Markdown body as design rationale: it explains mood, hierarchy,
+  interaction intent, and where tokens should or should not be used.
+- If no `DESIGN.md` exists this skill is inactive; for new UI, offer to
+  create one or ask for a brand/reference, but don't generate one
+  unprompted.
+
+## Default: read-only
+**Do not modify `DESIGN.md` unless the user explicitly asks for a design
+system change.** Implementation work consumes the contract; it does not
+edit it. Token additions, renames, or section restructures land in their
+own commit with a clear message and (ideally) a Stitch round-trip.
+
+## Implementation rules
+1. Map tokens into the local styling system already in use: CSS variables,
+   Tailwind theme values, design-token JSON, component props, or native
+   styles.
+2. Use token references and component patterns from `DESIGN.md` instead of
+   hard-coded one-off values.
+3. Keep accessibility constraints intact. Do not weaken contrast, focus,
+   reduced-motion, or touch-target guidance unless the user explicitly
+   asks.
+
+## When an edit IS authorised
+1. Preserve unknown headings and extra prose; other agents or Stitch may
+   own them.
+2. Express component variants as related entries
+   (`button-primary`, `button-primary-hover`, etc.).
+3. Land token / structure changes in their own commit, separate from the
+   feature consuming them.
+
+## Validation
+- If Node/npm tooling is available, lint with:
+
+  ```bash
+  npx @google/design.md lint DESIGN.md
+  ```
+
+- For design system changes, diff before/after:
+
+  ```bash
+  npx @google/design.md diff DESIGN.before.md DESIGN.md
+  ```
+
+- If the CLI is unavailable or network/dependency policy blocks it, the
+  manual fallback is best-effort only — check for broken `{path.to.token}`
+  references, missing primary color / typography tokens, duplicate section
+  headings, and section order. The CLI ALSO checks contrast ratios and
+  orphaned tokens; the manual fallback does not, so re-run the CLI when
+  you regain network access.
+
+## Expected sections
+The Google draft spec uses YAML front matter plus Markdown sections.
+Common sections:
+
+- `## Overview`
+- `## Colors`
+- `## Typography`
+- `## Layout`
+- `## Elevation & Depth`
+- `## Shapes`
+- `## Components`
+- `## Do's and Don'ts`
+
+## Self-rewrite hook
+After every 5 uses OR on any failure:
+1. Read the last N skill-specific episodic entries.
+2. If a new failure mode has appeared (e.g. tokens drifting away from
+   DESIGN.md, accessibility rules being weakened, unauthorised edits to
+   the contract file), append it to this skill's `KNOWLEDGE.md`.
+3. If a constraint was violated, escalate to `semantic/LESSONS.md`.
+4. Commit: `skill-update: design-md, <one-line reason>`.