JS-1513 peach-check skill: filter ANSI script-preview lines, clarify parallelism rule

.claude/skills/peach-check/SKILL.md

@@ -29,6 +29,12 @@ Before running this skill, ensure:
 separate Bash call. Chaining bypasses the per-tool permission prompts that allow the user to
 review each action individually.
 
+**Parallel execution is separate from chaining.** Issuing multiple independent Bash calls in
+the same response message is the correct way to run jobs concurrently — it does not violate the
+no-chaining rule. The no-chaining rule is about what goes *inside* a single Bash call; parallel
+execution is about how many Bash calls appear in a single response. Both rules apply together:
+separate calls, issued at the same time.
+
 ## Invocation
 
 ```
@@ -131,7 +137,7 @@ Instead:
 
 **Step 5 — Read the classification guide and triage all logs**
 
-Read `docs/peach-main-analysis.md` once to load the failure categories and decision flowchart.
+Read `docs/peach-main-analysis.md` (at the repository root) once to load the failure categories and decision flowchart.
 
 Create the work directory where logs will be stored for inspection:
 
@@ -155,6 +161,7 @@ via the `e` command, which is a risk when processing untrusted log content:
 gh api "repos/SonarSource/peachee-js/actions/jobs/JOB_ID/logs" \
   > target/peach-logs/JOB_ID.log
 sed --sandbox -n '
+/\[36;1m/b
 /Process completed with exit code/p
 /EXECUTION FAILURE/p
 /OutOfMemoryError/p
@@ -183,6 +190,7 @@ SonarJS plugin stack trace. The log is already on disk from Phase 1 — no re-do
 
 ```bash
 sed --sandbox -n '
+/\[36;1m/b
 /Sensor /p
 /EXECUTION FAILURE/p
 /OutOfMemoryError/p
@@ -271,5 +279,5 @@ The release recommendation is:
 **Step 9 — Update docs if a new failure pattern was found**
 
 If any job was classified as NEEDS-MANUAL-REVIEW and you identified its root cause during this
-session, update `docs/peach-main-analysis.md` with a new category entry. This keeps the
+session, update `docs/peach-main-analysis.md` (at the repository root) with a new category entry. This keeps the
 classification guide current for future runs.

.gitignore

@@ -78,3 +78,6 @@ lcov.info
 .claude/*
 !.claude/*.md
 !.claude/skills/
+
+.codex/
+.mcp.json

docs/peach-main-analysis.md

@@ -364,6 +364,7 @@ Identifies which step failed and what exit code was produced. Run on every faile
 
 ```bash
 sed --sandbox -n '
+/\[36;1m/b                             # skip GitHub Actions script-preview lines (ANSI-colored)
 /Process completed with exit code/p    # universal — exit code value drives the flowchart
 /EXECUTION FAILURE/p                   # scanner ran and failed (exit code 3)
 /OutOfMemoryError/p                    # OOM / Runner Killed
@@ -390,6 +391,7 @@ jobs where Phase 1 showed exit code 3 without a clear misconfiguration signal.
 
 ```bash
 sed --sandbox -n '
+/\[36;1m/b                             # skip GitHub Actions script-preview lines (ANSI-colored)
 /Sensor /p                             # last sensor name — is it a SonarJS sensor?
 /EXECUTION FAILURE/p                   # scanner failure marker
 /OutOfMemoryError/p                    # OOM inside scanner