You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**OpenClaw** responds with: pass/fail, exact query/payload, expected vs actual, UTC timestamps, bench URLs/context, and harness-drift vs product-defect classification.
64
+
-**OpenClaw does not edit product code** during this loop unless the human explicitly changes that rule.
65
+
-**Cursor does not assume parity failures are product bugs** until OpenClaw confirms healthy auth preflight and bench context.
Copy file name to clipboardExpand all lines: openclaw/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ OpenClaw may run on a different machine than Open-FDD. For split setup details s
23
23
## Current bench reality (keep this straight)
24
24
25
25
- Bench/frontend/backend/BACnet reachability can be healthy while auth context is still wrong.
26
-
-Current direct authenticated check has failed with `FORBIDDEN: Invalid API key`.
27
-
-Treat this as **launcher/env/runtime-context drift** unless proven otherwise.
26
+
-Missing or invalid `OFDD_API_KEY` should be treated as **launcher/env/runtime-context drift** unless proven otherwise.
27
+
-If Open-FDD is running on another machine, load the active `.env` into the shell or point `OPENCLAW_STACK_ENV` at it before calling auth-sensitive APIs.
28
28
-**Do not delete or bury issue `#92`**; keep it as likely real product parity tracking once auth is healthy.
29
29
- Do not frame auth-context drift itself as a confirmed product bug without clean repro under known-good auth.
Copy file name to clipboardExpand all lines: openclaw/SKILL.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,9 @@ Do not blend security hardening notes into unrelated defect triage without clear
77
77
- Do not treat coding changes as the primary goal.
78
78
- Keep issue/evidence trail in `openclaw/issues_log.md`.
79
79
- Use `openclaw/HANDOFF_PROTOCOL.md` for Cursor/OpenClaw handoff discipline.
80
+
- In the current operating model: **Cursor = product engineer, OpenClaw = tester**.
81
+
- When Cursor provides a commit SHA + issue IDs + acceptance criteria, retest the live bench against that SHA, do **no product-code edits**, and post evidence back to GitHub.
82
+
- Healthy auth preflight is required before drawing frontend/API parity conclusions.
0 commit comments