mirror of
https://github.com/Kpa-clawbot/meshcore-analyzer.git
synced 2026-05-12 18:55:25 +00:00
Kpa-clawbot
f701121672
Adds the CoreScope-side artifacts that pair with the generic [`qa-suite` skill](https://github.com/Kpa-clawbot/ai-sdlc/pull/1). ## Layout ``` qa/ ├── README.md ├── plans/ │ └── v3.6.0-rc.md # 34-commit test plan since v3.5.1 └── scripts/ └── api-contract-diff.sh # CoreScope-tuned API contract diff ``` The skill ships the reusable engine + qa-engineer persona + an example plan. This PR adds the CoreScope-tuned plan and the CoreScope-tuned script (correct seed lookups for our `{packets, total}` response shape, our endpoint list, our `resolved_path` requirement). Read by the parent agent at runtime. ## How to use From chat: - `qa staging` — runs the latest `qa/plans/v*-rc.md` against staging, files a fresh GH issue with the report - `qa pr <N>` — uses `qa/plans/pr-<N>.md` if present, else latest RC plan; comments on the PR - `qa v3.6.0-rc` — runs that specific plan The qa-engineer subagent walks every step, classifying each as `auto` (script) / `browser` (UI assertion) / `human` (manual) / `browser+auto`. Quantified pass criteria are mandatory — banned phrases: 'visually aligned' / 'fast' / 'no regression'. ## Plan v3.6.0-rc contents Covers the 34 commits since v3.5.1: - §1 Memory & Load (#806, #790, #807) — heap thresholds, sawtooth pattern - §2 API contract (#806) — every endpoint that should carry `resolved_path`, auto-checked by `api-contract-diff.sh` - §3 Decoder & hashing (#787, #732, #747, #766, #794, #761) - §4 Channels (#725 series M1–M5) - §5 Clock skew (#690 series M1–M3) - §6 Observers (#764, #774) - §7 Multi-byte hash adopters (#758, #767) - §8 Frontend nav & deep linking (#739, #740, #779, #785, #776, #745) - §9 Geofilter (#735, #734) - §10 Node blacklist (#742) - §11 Deploy/ops Release blockers: §1.2, §2, §3. §4 is the headline-feature gate. ## Adding new plans Per release: copy `plans/v<last>-rc.md` to `plans/v<new>-rc.md` and update commit-range header, new sections, GO criteria. Per PR: create `plans/pr-<N>.md` with the bare minimum for that PR's surface area. Co-authored-by: you <you@example.com>
46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
# CoreScope QA artifacts
|
|
|
|
Project-specific assets for the [`qa-suite`](https://github.com/Kpa-clawbot/ai-sdlc/tree/master/skills/qa-suite) skill.
|
|
|
|
## Layout
|
|
|
|
```
|
|
qa/
|
|
├── README.md ← this file
|
|
├── plans/
|
|
│ └── <release>.md ← per-release test plans (one file per RC)
|
|
└── scripts/
|
|
└── api-contract-diff.sh ← CoreScope-tuned API contract diff
|
|
```
|
|
|
|
## How to run
|
|
|
|
```
|
|
qa staging # use the latest plans/v*-rc.md against staging
|
|
qa pr 806 # use plans/pr-806.md if it exists, else latest plans/v*-rc.md
|
|
qa v3.6.0-rc # use plans/v3.6.0-rc.md
|
|
```
|
|
|
|
The parent agent loads the qa-suite skill, which reads:
|
|
1. The plan file from `qa/plans/`
|
|
2. Bundled scripts from `qa/scripts/`
|
|
3. The reusable engine + qa-engineer persona from the skill itself
|
|
|
|
## Adding a new plan
|
|
|
|
For each release candidate, copy the latest `plans/v*-rc.md` to `plans/<new-tag>.md` and update:
|
|
- The commit-range header (`vN.M..master`)
|
|
- Any new sections for new features in the release
|
|
- The "Test data" section if new fixture types are needed
|
|
- The GO criteria (which sections are blockers)
|
|
|
|
## Adding a new script
|
|
|
|
Custom scripts go in `qa/scripts/` with `mode=auto: <script-name>` referenced from the plan. The qa-engineer subagent runs them with two args: `BASELINE_URL TARGET_URL`.
|
|
|
|
Authoring rules from the qa-suite skill:
|
|
- 4-way error classification: `curl-failed` / `parse-empty` / `shape-diff` / field-missing
|
|
- Distinguish HTTP errors from jq parse failures
|
|
- Don't silence stderr — script bugs must surface
|
|
- Exit code = number of failures
|