opensquid 0.5.395

package/packs/builtin/scope-architect/skills/pre-research-authoring/skill.yaml

@@ -0,0 +1,142 @@
+# pre-research-authoring — two soft warns guarding pre-research docs:
+#   1. warn-preresearch-write-without-research (DPC.5): insufficient
+#      research-tool activity this turn (did you DO the research?).
+#   2. warn-scope-incomplete (SG.1, 2026-06-01): the doc doesn't answer the
+#      three hole-finding questions — ## Alternatives / ## Failure modes /
+#      ## Empirical spikes (does the doc ANSWER them?).
+#
+# SG.1 also FIXED rule 1's `text_field: 'targs.file_path'` → `'args.file_path'`:
+# `targs.X` is a binding path, but text_pattern_match resolves text_field only
+# against ctx.event fields — so rule 1 silently never fired. Both rules now use
+# the event path `args.X` (the working convention, cf. inline-spec-block).
+#
+# Per T-DISCIPLINE-PIPELINE-COMPLETION DPC.5 (2026-05-30): closes the gap
+# where the agent writes pre-research files from intuition instead of
+# from actual research. Pre-research is the OUTPUT of doing research —
+# not a planning doc authored from prior beliefs.
+#
+# Trigger: PreToolUse on Write/Edit targeting paths matching
+# docs/research/[^/]*-pre-research-[^/]*\.md$ — the standard
+# pre-research file naming convention enforced by inline-spec-block +
+# scope-decomposer chain handoffs.
+#
+# Check: session_tool_history filtered to [mcp__opensquid__recall, Read,
+# Grep]. Threshold 3 = heuristic for sufficient research (at least one
+# recall + a couple of code reads/greps). Below threshold → warn.
+#
+# Verdict level: warn (soft surface). A legitimate session-2 continuation
+# pre-research can have just 1 recall (resuming prior session's research);
+# warn surfaces but allows write to proceed.
+name: pre-research-authoring
+load: preload
+when_to_load:
+  - tool_match: Write
+  - tool_match: Edit
+triggers:
+  - kind: tool_call
+rules:
+  - id: warn-preresearch-write-without-research
+    process:
+      - call: tool_name
+        as: tool
+      # FIX (SG.1, 2026-06-01): was `targs.file_path` — a BINDING path that
+      # text_pattern_match cannot resolve (it reads ctx.event fields only), so
+      # this guard silently never matched and the warn never fired. The event
+      # field is `args.file_path` (see inline-spec-block for the correct
+      # convention). Now the rule actually fires.
+      - call: text_pattern_match
+        args:
+          text_field: 'args.file_path'
+          patterns:
+            - 'docs/research/[^/]*-pre-research-[^/]*\.md$'
+        as: is_preresearch
+      - call: session_tool_history
+        if: '(tool == "Write" || tool == "Edit") && len(is_preresearch.matched) > 0'
+        args:
+          scope: current_turn
+          filter_names:
+            - mcp__opensquid__recall
+            - Read
+            - Grep
+        as: research
+      - call: verdict
+        if: '(tool == "Write" || tool == "Edit") && len(is_preresearch.matched) > 0 && research.count < 3'
+        args:
+          level: warn
+          message: >-
+            PRE-RESEARCH AUTHORING (DPC.5): about to write a pre-research
+            doc with insufficient research-tool activity this turn (recall +
+            Read + Grep combined < 3 calls).
+
+            Pre-research is the OUTPUT of doing the research — not a planning
+            doc you write from intuition. If you haven't done at least:
+            (1) recall on the topic; (2) Read of relevant local files;
+            (3) Grep of the codebase for prior art —
+            you're authoring intuition, not research. The downstream
+            task-spec-author then gets incomplete data → tasks built on
+            drift.
+
+            Required: recall + read + grep FIRST, THEN write the pre-research
+            doc summarizing findings + residual gaps. Warn surfaces but does
+            not block (a session-2 continuation pre-research may legitimately
+            ride on session-1 research; pass through with awareness).
+  # SG.1 (2026-06-01) — scope-completeness check. Complements the
+  # research-activity warn above: that one asks "did you DO research?"; this
+  # one asks "does the doc ANSWER the three hole-finding questions?"
+  - id: warn-scope-incomplete
+    process:
+      - call: tool_name
+        as: tool
+      - call: text_pattern_match
+        args:
+          text_field: 'args.file_path'
+          patterns:
+            - 'docs/research/[^/]*-pre-research-[^/]*\.md$'
+        as: is_preresearch
+      # On a Write of a pre-research doc, the event carries the full doc in
+      # args.content → scan it for the three section headers. Write-only: Edit
+      # carries partial content (new_string), so the full-doc check is
+      # unreliable there (block-at-authoring-advance follow-up covers Edit).
+      - call: text_pattern_match
+        if: 'tool == "Write" && len(is_preresearch.matched) > 0'
+        args:
+          text_field: 'args.content'
+          patterns:
+            - '##\s+Alternatives'
+            - '##\s+Failure modes'
+            - '##\s+Empirical spikes'
+        as: sections
+      - call: verdict
+        if: 'tool == "Write" && len(is_preresearch.matched) > 0 && len(sections.matched) < 3'
+        args:
+          level: warn
+          message: >-
+            SCOPE COMPLETENESS (SG.1): this pre-research doc is missing one
+            or more hole-finding sections. A complete scope answers all three
+            BEFORE authoring tasks:
+            ## Alternatives (>=2 options + why this one wins);
+            ## Failure modes (inversion — each "how does this fail?" answered);
+            ## Empirical spikes (each empirical open-question resolved by a
+            cheap throwaway spike before locking the design).
+            Holes found at scope are the cheapest you will ever fix — add the
+            missing section(s), then re-write. (Warn, not block: the doc must
+            stay authorable.)
+prose: |
+  Two soft gates on pre-research authoring:
+
+  - warn-preresearch-write-without-research (DPC.5): threshold of 3
+    research-tool calls is heuristic — biases toward "agent did some
+    looking around" without being so strict that legitimate continuation
+    pre-research gets noisily warned. (SG.1 fixed its silent-no-op
+    text_field bug; it now actually fires.)
+  - warn-scope-incomplete (SG.1): on a Write of a pre-research doc, checks
+    args.content for the three hole-finding section headers (Alternatives /
+    Failure modes / Empirical spikes). Warn, never block — the doc must
+    stay authorable. Write-only: Edit carries partial content; a hard block
+    that reads the full artifact from disk at the authoring-advance gate is
+    a follow-up (needs a file-content-reading primitive). Header-presence
+    only (v1) — section non-emptiness is a later refinement.
+
+  Both fire only on the pre-research path convention; both are soft
+  (warn) — they surface, never block. False-positive cost: an extra
+  context injection. False-negative cost: no worse than baseline.

package/packs/builtin/scope-architect/skills/scope-before-code/skill.yaml

@@ -0,0 +1,34 @@
+# scope-before-code — AP.5 Gate A. In automation mode, blocks code-writes
+# (src/**) whose active task has no generator provenance (a docs/tasks spec on
+# disk). Extracted from user-pack scope-decomposer rule `scope-before-code`
+# (DPC.1).
+name: scope-before-code
+load: preload
+when_to_load:
+  - tool_match: Write
+  - tool_match: Edit
+triggers:
+  - kind: tool_call
+rules:
+  - id: block-code-without-scope
+    process:
+      - call: tool_name
+        as: tool
+      - call: tool_args
+        as: targs
+      - call: is_automation_mode
+        as: auto
+      - call: has_generated_spec
+        if: 'auto.value == true && (tool == "Write" || tool == "Edit") && contains(targs.file_path, "src/")'
+        as: prov
+      - call: verdict
+        if: 'auto.value == true && (tool == "Write" || tool == "Edit") && contains(targs.file_path, "src/") && prov.generated == false'
+        args:
+          level: block
+          message: >-
+            BLOCKED: coding before scope→task. This work's active task has no
+            generator provenance (a docs/tasks spec on disk). Run
+            pre-research → task-spec-author profession FIRST, create the task
+            with its ABSOLUTE spec path in metadata.spec, load it
+            (set in_progress), THEN code. If there is no active task,
+            scope one first.

package/packs/builtin/scope-architect/skills/scope-detect/skill.yaml

@@ -0,0 +1,73 @@
+# scope-detect — soft prompt-intent warn that fires on scope-authoring intent.
+# Extracted from user-pack scope-decomposer rule `scope-intent-nudge` (DPC.1).
+name: scope-detect
+load: preload
+when_to_load:
+  - kind: event_type
+    type: prompt_submit
+triggers:
+  - kind: prompt_submit
+rules:
+  - id: scope-intent-nudge
+    process:
+      - call: text_pattern_match
+        args:
+          text_field: prompt
+          patterns:
+            # Original scope-decomposer patterns (user-pack source):
+            - '\bspec(?:c?ing|ced)?\s+(?:out|this|the)\b'
+            - '\bscope\s+(?:out|this|the|a)\b'
+            - '\bnew\s+(?:task|track)\b'
+            - '\badd\s+(?:a\s+|another\s+)?(?:task|track)\b'
+            - '\bdesign\s+(?:a|the|this)\b'
+            - '\bplan\s+(?:out|a|the)\b'
+            # DPC.2 (2026-05-30) — bulk-action patterns from drift transcripts.
+            # Today's session proved these prompts bypassed the original 6
+            # patterns ("audit and add a proper solution", "refactor based on
+            # it all", "close the gaps based your understanding").
+            - '\baudit\s+(?:memory|skills|tasks|gaps|coverage|drift|the\s+\w+)\b'
+            - '\b(?:close|fix|address|propose|build|ship)\s+(?:the\s+)?(?:gaps?|drift|items|todos|skills|gates)\b'
+            - '\bproper\s+solution\b'
+            - '\b(?:list|batch)\s+of\s+(?:tasks|todos|items|skills|gates|issues|memories|gaps|drifts?)\b'
+            - '\brefactor\b'
+            - '\bbased\s+(?:on\s+)?(?:your|the)\s+(?:understanding|picture|synthesis|integration)\b'
+            # SAR.1 (2026-05-30) — ship/make-it-work intent family. This
+            # session's prompt "forbidden from pausing my workflow until you
+            # have open squid fully functional as intended" fell into the
+            # regex hole — none of the prior 12 patterns matched. The family
+            # below catches the meta-intent of "deliver the whole thing".
+            - '\b(?:fully|completely|properly)\s+(?:functional|working|operational|wired|complete|done)\b'
+            - '\b(?:make|get|ship|bring)\s+(?:.+\s+)?(?:functional|working|operational|complete|done|live|ready|v\d+(?:\.\d+)*)\b'
+            - '\bforbidden\s+from\s+(?:pausing|stopping|asking|delegating)\b'
+            # 2026-05-31 narrowing: bare \bas\s+intended\b was too broad —
+            # falsely fired on "working as intended" (tech idiom for "behaves
+            # correctly"), blocking a legitimate user frustration message. Two
+            # narrower patterns split the intent:
+            # (a) delivery-verb form: "ship/build/deliver/finish X as intended"
+            # (b) delivery-adjective form: "fully/completely/properly <state> as
+            #     intended" — the SAR.1 source phrase "fully functional as intended"
+            # Tech idioms ("working as intended", "behaves as intended", "functions
+            # as intended") have neither pattern → correctly excluded.
+            - '\b(?:deliver(?:ed)?|ship(?:ped)?|build|built|finish(?:ed)?|complete[ds]?)\s+(?:.+\s+)?(?:as|to be|to-be)\s+intended\b'
+            - '\b(?:fully|completely|properly)\s+(?:functional|operational|working|complete|wired|done|ready|live)\s+(?:as|to be|to-be)\s+intended\b'
+            - '\b(?:remaining|outstanding|leftover)\s+(?:phases?|tracks?|work|tasks?|todos?)\b'
+            - '\b(?:rest|remainder)\s+of\s+(?:the\s+)?(?:plan|track|phase|work|todos?)\b'
+            - '\b(?:every|all)\s+(?:remaining|leftover|outstanding)\s+(?:phases?|tracks?|tasks?|work)\b'
+        as: intent
+      - call: verdict
+        if: 'len(intent.matched) > 0'
+        args:
+          level: warn
+          message: >-
+            Scope-authoring intent detected. Before writing ANY task / track /
+            spec: (1) run pre-research → docs/research/<slug>-pre-research-<date>.md;
+            (2) invoke the `task-spec-author` profession (next_action.profession);
+            (3) verify all 11 fields. Do NOT inline-spec in TASKS.md or
+            docs/tasks/. opensquid emits this directive; YOU run the steps.
+prose: |
+  The SOFT side of the scope-authoring gate. Fires on prompt_submit when
+  the user's message shows scope-authoring intent. The HARD side
+  (inline-spec-block) blocks the actual Write/Edit when a spec lands with no
+  pre-research artifact. DPC.2 widens this skill's regex patterns to cover
+  bulk-action prompts; this initial DPC.1 version preserves the original
+  user-pack patterns to keep the promotion behavior-equivalent.

package/packs/builtin/scope-architect/skills/task-list-generated/skill.yaml

@@ -0,0 +1,28 @@
+# task-list-generated — AP.5 Gate B. Every OPEN task must carry a
+# metadata.taskId provenance stamp. `warn`: Gate A hard-blocks the write;
+# Gate B surfaces list hygiene so the agent regenerates smuggled tasks.
+# Extracted from user-pack scope-decomposer rule `task-list-generated` (DPC.1).
+name: task-list-generated
+load: preload
+when_to_load:
+  - kind: event_type
+    type: prompt_submit
+triggers:
+  - kind: prompt_submit
+rules:
+  - id: warn-task-list-not-fully-generated
+    process:
+      - call: is_automation_mode
+        as: auto
+      - call: task_list_generated
+        if: 'auto.value == true'
+        as: list
+      - call: verdict
+        if: 'auto.value == true && list.all_generated == false'
+        args:
+          level: warn
+          message: >-
+            Task-list hygiene: one or more open tasks have NO generator
+            provenance (missing metadata.taskId) — not produced by
+            scope→task-spec-author. Regenerate them through the pipeline
+            (or stamp metadata.taskId) so the whole list is task-generated.

package/packs/builtin/scope-architect/skills/taskcreate-spec-required/skill.yaml

@@ -0,0 +1,27 @@
+# taskcreate-spec-required — blocks raw TaskCreate without metadata.spec.
+# Extracted from user-pack scope-decomposer rule
+# `taskcreate-requires-spec-provenance` (SDTC.1, DPC.1).
+name: taskcreate-spec-required
+load: preload
+when_to_load:
+  - tool_match: TaskCreate
+triggers:
+  - kind: tool_call
+rules:
+  - id: block-taskcreate-without-spec
+    process:
+      - call: tool_name
+        as: tool
+      - call: tool_args
+        as: targs
+      - call: verdict
+        if: 'tool == "TaskCreate" && (targs.metadata == null || targs.metadata.spec == null || len(targs.metadata.spec) == 0)'
+        args:
+          level: block
+          message: >-
+            BLOCKED: TaskCreate without `metadata.spec` bypasses the
+            discipline pipeline. Run pre-research → task-spec-author →
+            `docs/tasks/T-<slug>.md` FIRST, then TaskCreate with
+            metadata: { spec: '<absolute spec path>', taskId: '<task id>' }.
+            The provenance stamp lets every open task carry a verifiable
+            link back to its source spec.

package/packs/builtin/scope-architect/team.yaml

@@ -0,0 +1,65 @@
+# MM.3 — Mode A team manifest for the scope-architect profession.
+#
+# Phase 2 ships scope-architect as a single-role profession (leaf-node per
+# T-MULTIMODE L19). Multi-role professions (e.g. spawning a sub-profession
+# for residual-gap detection) are Phase 4+.
+#
+# The spawned subagent loads the scope-architect pack itself (self-reference
+# is intentional in Mode A — the profession's own discipline applies to its
+# subagent context). `model_alias: reasoning` resolves at spawn time via the
+# user's models.yaml (model-neutral per [[feedback_stop_haiku_drift]] +
+# [[project_opensquid_model_neutral_subagent_primitive]]).
+#
+# When the parent agent receives a directive like
+# `{profession: 'scope-architect', rationale: '...'}` it invokes
+# `spawn_subagent({ role: 'scope-architect', ... })` against this team.
+# opensquid never invokes spawn_subagent itself — the agent does the
+# spawning per [[project_opensquid_no_agent_loop]].
+name: scope-architect-team
+roles:
+  - name: scope-architect
+    pack: scope-architect
+    model_alias: reasoning
+    handoff_signal: SCOPE_COMPLETE
+    instructions: |
+      You are the scope-architect subagent. The parent agent spawned you
+      via a chain-handoff directive because scope-first authoring is
+      required for the current task.
+
+      Your charter:
+        1. Read the parent's most recent user message + the active task
+           context (if any) to understand the work the parent is
+           preparing to authorize.
+        2. Produce a pre-research artifact at
+           docs/research/<track-id>-pre-research-<YYYY-MM-DD>.md
+           covering: surface area (every file you would touch); locked
+           decisions (L1-Ln — your authoritative calls); proposed task
+           decomposition; residual gaps + defaults.
+        3. Emit handoff_signal `SCOPE_COMPLETE` followed by the
+           pre-research artifact path on a final line so the parent can
+           chain into task-spec-author.
+
+      Discipline:
+        - No code changes. No tool calls outside Read + Write + Bash for
+          docs/.
+        - Cite source paths + line ranges for every surface-area claim.
+        - Lock decisions, do not leave them open. Each L<n> is a chosen
+          path with rationale.
+        - Per [[feedback_synthesis_step_required]]: after reading, do an
+          explicit SYNTHESIS step before drafting the artifact.
+        - Per [[feedback_no_skim_during_research]]: full end-to-end
+          reads of cited files; no skimming.
+        - RESEARCH METHOD (this is HOW, not just what — it avoids the
+          per-turn depth gate AND the audit re-spawn): do ALL your research —
+          recall + Read + Grep, AT LEAST 3 calls — in the SAME turn as the
+          pre-research Write. The depth gate counts research-tool calls THIS
+          turn only; it cannot see prior turns. Then write the artifact ONCE
+          from that batched research. Do NOT write a stub and edit it across
+          later "bare" turns: each such edit re-trips the depth gate and (before
+          cached_audit) re-spawned the 170s reviewer. Batch first, write once.
+        - The artifact MUST contain, or the audit blocks it: alternatives (>=2)
+          weighed against the criteria with the SIMPLEST-correct chosen;
+          failure-modes / inversion; an empirical-spike note; a scope boundary;
+          and EVERY claim cited (file:line / memory / the user's words) or
+          flagged OPEN QUESTION — and an OPEN QUESTION must be resolved with the
+          user IN SCOPE before the write, never carried into the artifact.

package/packs/builtin/seo-aeo-expert/drift_response.yaml

@@ -0,0 +1,11 @@
+# seo-aeo-expert drift policy — block ONLY irreversible/invisible damage
+# (robots-level de-indexing, citation-bot blocking: silent total-visibility
+# loss with no acceptable accidental path). Everything else warns: SEO is
+# judgment-heavy — the pack informs, the human decides. The §4.3 push gate
+# (push-while-unvalidated) starts at warn for the dogfood week (spec §10.6)
+# and is promoted to block_tool after false-positive review.
+default: warn
+
+per_rule:
+  citation-bot-disallow: block_tool
+  robots-wildcard-disallow: block_tool

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_allow_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_allow_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "citation-bot-disallow",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: OAI-SearchBot\nAllow: /\n\nUser-agent: GPTBot\nDisallow: /\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_cross_section_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_cross_section_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "citation-bot-disallow",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: PerplexityBot\nAllow: /\nUser-agent: *\nDisallow: /admin\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_robots_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/citation_robots_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "citation-bot-disallow",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: OAI-SearchBot\nDisallow: /\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/training_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/training_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "training-bot-change",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: GPTBot\nDisallow: /\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/training_unrelated_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/training_unrelated_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "training-bot-change",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "vercel.json",
+      "content": "{\"redirects\": []}"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/wildcard_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/wildcard_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "robots-wildcard-disallow",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: *\nDisallow: /\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/wildcard_path_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/bot-policy-guard/wildcard_path_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "robots-wildcard-disallow",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "public/robots.txt",
+      "content": "User-agent: *\nDisallow: /admin\n"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/no_claims_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/no_claims_pass.input.json

@@ -0,0 +1,14 @@
+{
+  "if": "(claim_w.matched.length > 0 || claim_e.matched.length > 0) && gt.exists == false",
+  "bindings": {
+    "claim_w": {
+      "matched": []
+    },
+    "claim_e": {
+      "matched": []
+    },
+    "gt": {
+      "exists": false
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/offer_no_doc_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/offer_no_doc_fire.input.json

@@ -0,0 +1,14 @@
+{
+  "if": "(claim_w.matched.length > 0 || claim_e.matched.length > 0) && gt.exists == false",
+  "bindings": {
+    "claim_w": {
+      "matched": ["\"@type\"\\s*:\\s*\"Offer\""]
+    },
+    "claim_e": {
+      "matched": []
+    },
+    "gt": {
+      "exists": false
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/offer_with_doc_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/ground-truth-gate/offer_with_doc_pass.input.json

@@ -0,0 +1,14 @@
+{
+  "if": "(claim_w.matched.length > 0 || claim_e.matched.length > 0) && gt.exists == false",
+  "bindings": {
+    "claim_w": {
+      "matched": ["\"price\"\\s*:"]
+    },
+    "claim_e": {
+      "matched": []
+    },
+    "gt": {
+      "exists": true
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/desc_long_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/desc_long_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "meta-description-length",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "src/app/layout.tsx",
+      "content": "description: 'Raum Pilates is a boutique reformer pilates studio in Englewood Cliffs New Jersey offering private one on one sessions group classes and barre with bilingual English and Korean instruction for every level.'"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/desc_ok_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/desc_ok_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "meta-description-length",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "src/app/layout.tsx",
+      "content": "description: 'Boutique reformer pilates studio in Englewood Cliffs, NJ.'"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/img_alt_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/img_alt_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "meta-img-alt",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "src/components/Hero.html",
+      "content": "<img src=\"/hero.jpg\" class=\"w-full\">"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/img_alt_pass.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": false
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/img_alt_pass.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "meta-img-alt",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "src/components/Hero.html",
+      "content": "<img src=\"/hero.jpg\" alt=\"Reformer studio interior\">"
+    }
+  }
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/title_long_fire.expected.json

@@ -0,0 +1,3 @@
+{
+  "verdict": true
+}

package/packs/builtin/seo-aeo-expert/fixtures/meta-quality-gate/title_long_fire.input.json

@@ -0,0 +1,10 @@
+{
+  "rule": "meta-title-length",
+  "event": {
+    "tool": "Write",
+    "args": {
+      "file_path": "src/app/layout.tsx",
+      "content": "export const metadata = { title: 'Raum Pilates Englewood Cliffs New Jersey Boutique Reformer Studio And Wellness Center' }"
+    }
+  }
+}