v0.1.0

Initial release of the ecommerce-process-mining skill: consented DOM-event capture
from the admin tools an e-commerce back office already uses, a gap-capture form for the
work a browser cannot see, and a batch pipeline that turns both into per-role SOPs and a
ranked automation shortlist.

Added

• SKILL.md entry point: the architecture diagram, ten critical facts, six hard rules,
  the quick-start order, and the reference directory table mapping trigger keywords to
  references/.
• references/adaptation.md: the seam contract with the host app, the capability table,
  the canonical rename table, the background jobs, module placement shared by the app and
  the extension, and the host probe.
• references/consent-and-privacy.md: the employee and the customer on the screen, the
  four capture layers in order, pause against revoke against disconnect, the
  excluded-domain module shared by both sides, what the employee must be told, and the
  legal layer per jurisdiction.
• references/data-model.md: the neutral TypeScript shapes, the Postgres schema with
  row-level security, the append-only consent ledger and its immutability trigger, the
  suppressing enrollment function, the Supabase wiring and the Firestore differences.
• references/console-surfaces.md: the employee page and the manager page, the
  server-confirmed consent toggle, the gap-capture form and its validation, automation
  ranking, the help page, and their suites.
• references/ingest.md: the ingest contract, the consent re-read per batch, per-event
  validation, the age window, idempotency, 207 with retry indexes, counters and
  retention.
• references/pii-scrubber.md: the scrubber, the card-against-barcode rule, IBAN, JWT
  and email masking, sensitive labels, credential URLs, per-deployment configuration and
  the known limits.
• references/extension-auth.md: the PKCE handshake, the extension-id allowlist, the
  single-statement claim, minting the scoped key, and revoking it.
• references/extension.md: Manifest V3 with its corrections, the tested control logic
  for pause, budget, queue and session rotation, label resolution and dom_confidence,
  the Chrome wiring, and the assumptions to settle in a spike.
• references/screenshots.md: the screenshot modes, the capture gate and throttle,
  viewport and crop perceptual hashing, bounding boxes, upload and retention.
• references/ai-pipeline.md: the three batch stages, routing on dom_confidence,
  embeddings, SOP output and the guardrails.
• references/ecommerce-playbook.md: which tools to capture in a shop, which processes
  to mine first, the default gap-form categories, the rollout order and the failure
  modes.
• references/testing.md: what is verified and how, the vitest suites with 76 cases, the
  24 SQL checks in verify.sql, and what to add in the host.
• references/provenance.md: the engineering ledger, the maturity tags, what the audit
  changed and how the templates verify it, what was kept deliberately, what was designed
  here and has never run, the unverified list, and the fix order for anyone maintaining
  the earlier implementation.
• Templates for lib/process-mining/*, db/process-mining/schema.sql and verify.sql,
  and the extension/ tree, written to compile under strict and
  noUncheckedIndexedAccess against zod 3 and zod 4.
• The properties the templates hold: consent per person and per tenant, re-read on every
  batch; one exclusion matcher imported by the extension and the ingest route; values
  that would need scrubbing never read; a scrubber that separates a card number from a
  barcode; a one-time code redeemable exactly once; a consent history nobody can rewrite;
  an ingest response that never claims an unstored event; and an enrollment count
  withheld when it would name the people.
• README.md: install, activation, the file table, the six non-negotiables,
  requirements, verification, the Not this table and the contributing conventions.
• CLAUDE.md: editing conventions for this repository.
• LICENSE: MIT.