Background
The results layer added in #12 (scripts/report.mjs) already records every Tester round into .clone-team/report.json. To plug clone-team runs into CI dashboards, it'd be great to also emit a CTRF (Common Test Report Format) JSON — the emerging standard test-report schema.
Scope (well-bounded)
- Add a
report.mjs ctrf --dir <projectDir> subcommand that reads report.json and writes .clone-team/report.ctrf.json in CTRF schema (map each section→test, each round→retry, verdict→passed/failed, issues→message).
- No change to the gate or existing commands — purely additive, JSON-then-render style like the existing
render.
- Add a test under
scripts/__tests__/ mirroring the existing report.test.mjs style.
Pointers
skills/clone-team/scripts/report.mjs (the json/render cases are the closest analogs)skills/clone-team/references/results-analysis.md (schema + upgrade path — this is listed there as a future hook)
Good first issue — self-contained, tested, no architecture risk.
Background
The results layer added in #12 (
scripts/report.mjs) already records every Tester round into.clone-team/report.json. To plug clone-team runs into CI dashboards, it'd be great to also emit a CTRF (Common Test Report Format) JSON — the emerging standard test-report schema.Scope (well-bounded)
report.mjs ctrf --dir <projectDir>subcommand that readsreport.jsonand writes.clone-team/report.ctrf.jsonin CTRF schema (map each section→test, each round→retry, verdict→passed/failed, issues→message).render.scripts/__tests__/mirroring the existingreport.test.mjsstyle.Pointers
skills/clone-team/scripts/report.mjs(thejson/rendercases are the closest analogs)skills/clone-team/references/results-analysis.md(schema + upgrade path — this is listed there as a future hook)Good first issue — self-contained, tested, no architecture risk.