Add amazon/order-history domain skill

[sfox100]

Adds a domain skill for extracting full order history from a logged-in Amazon session, field-tested against amazon.co.uk (2026-07-16) on a 2010-2026 account (1,007 orders).

Covers:

• Auth detection (signin redirect) and the one-time headed login pattern
• The timeFilter=year-YYYY + startIndex URL scheme, reading valid filter values from the #time-filter dropdown
• .order-card extraction JS for titles + order dates
• Traps: recent years (2024+) render a React layout with zero .order-card nodes (empty results are not "no orders"), late hydration needs a ~2s settle, and long multi-year scrapes should checkpoint to disk with flushed prints

🤖 Generated with Claude Code

---

Summary by cubic

Adds agent-workspace/domain-skills/amazon/order-history.md, a domain skill for extracting full Amazon order history from a logged-in session. Field-tested on amazon.co.uk (2010–2026, 1,007 orders) and amazon.com; runs now self-verify per-year counts.

• New Features

  • Auth detection via redirect to /ap/signin; one-time headed login reused.
  • Navigation: new_tab() for the first visit, then goto_url(); read #time-filter values; paginate with startIndex=0,10,....
  • Self-verifying runs: read expected count from .num-orders, use .a-pagination .a-last for the real end, assert collected vs expected.
  • Extraction: .order-card parsing for titles and order dates; json.loads around JSON.stringify; date regex supports UK and US formats.
  • Gotchas: wait ~2s for hydration; checkpoint long runs; don’t trust empty pages.

• Bug Fixes

  • Moved the file to agent-workspace/domain-skills/amazon/ so the harness loads it.
  • Removed the incorrect “2024+ React layout has no .order-card” note after re-testing; the count assertion guards against under-rendering.

^{Written for commit 734a31f. Summary will update on new commits.}

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="agent-workspace/domain-skills/amazon/order-history.md">

<violation number="1" location="agent-workspace/domain-skills/amazon/order-history.md:50">
P1: A missing `.num-orders` element is currently treated as a legitimate zero-order year: `count_text or "0"` makes the later `len(collected) != expected` check pass for an empty scrape. That defeats the self-verification and can silently produce a trusted but empty result when Amazon has not rendered the page or changes the selector. Missing/invalid count text could instead fail explicitly (while handling an explicit “no orders” response as zero).</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P1: A missing .num-orders element is currently treated as a legitimate zero-order year: count_text or "0" makes the later len(collected) != expected check pass for an empty scrape. That defeats the self-verification and can silently produce a trusted but empty result when Amazon has not rendered the page or changes the selector. Missing/invalid count text could instead fail explicitly (while handling an explicit “no orders” response as zero).

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At agent-workspace/domain-skills/amazon/order-history.md, line 50:

<comment>A missing `.num-orders` element is currently treated as a legitimate zero-order year: `count_text or "0"` makes the later `len(collected) != expected` check pass for an empty scrape. That defeats the self-verification and can silently produce a trusted but empty result when Amazon has not rendered the page or changes the selector. Missing/invalid count text could instead fail explicitly (while handling an explicit “no orders” response as zero).</comment>

<file context>
@@ -0,0 +1,111 @@
+```python
+import re
+count_text = js("document.querySelector('.num-orders')?.innerText")  # '186 orders' / '1 order'
+expected = int(re.sub(r"[^\d]", "", count_text or "0") or 0)
+```
+
</file context>