auto(polish): W24 #20 sotif-analysis-builder review pass, regen STATUS, journal

Autonomous daily run.
- POLISH: first polish-log entry for sotif-analysis-builder (severity low, no fix needed)
- Closes standing SOTIF zero-touch coverage mandate via documented review
- STATUS.md regenerated (76/76 paired, 100%); journal updated

Generated by automotive-skills-daily-standup scheduled task.

STATUS.md

@@ -1,6 +1,6 @@
 # STATUS — automotive-skills-suite
 
-_Auto-generated 2026-06-06 by automotive-skills-daily-standup._
+_Auto-generated 2026-06-09 by automotive-skills-daily-standup._
 
 | Builder | Domain | Paired Reviewer | Last Touched | Flag |
 |---------|--------|-----------------|--------------|------|
@@ -86,5 +86,5 @@ _Auto-generated 2026-06-06 by automotive-skills-daily-standup._
 - Builders: **76**, Reviewers: **76**, Paired ratio: **100.0%**
 - 🟢 Paired & fresh (≤30d): **2**  ·  🟡 Stale (>30d): **74**  ·  🔴 Orphan builders: **0**
 - Domain spread: safety=15, quality=10, comms=8, cyber=6, autosar=5, diagnostics=5, program-mgmt=5, v&v=5, aspice=4, sysml=4, calibration=3, mbse=3, sotif=3
-- Date: 2026-06-06
+- Date: 2026-06-09
 - Source: scan of `skills/` directory + `git log -1` per file.

docs/AUTONOMOUS_LOG.md

@@ -455,3 +455,48 @@ Standout finding is non-DoD and more impactful than the trigger gaps: the SKILL.
 - Mon W24 PLAN: include at least one SOTIF target (sotif-analysis or triggering-conditions) — zero-touch in May per the monthly KPI; a second zero-touch month justifies a tracking issue.
 - Sun TRIAGE (tomorrow): confirm the 13 → 12 issue-count delta (presumed external close of #17) and refresh labels.
 - Fmeda medium findings need maintainer action, esp. the SMvDU source-check against ISO 26262-5:2018 Annex B.
+
+## 2026-06-07 (autonomous run, TRIAGE)
+
+**Mode:** TRIAGE
+**Action:** Sunday triage pass — refreshed labels on all 12 open issues (one label added: `description-quality` to #12), confirmed the 13→12 issue-count delta from Thu/Fri, regenerated STATUS.md.
+**Files touched:** STATUS.md, docs/AUTONOMOUS_LOG.md (this entry)
+**Tests:** N/A (no test suite in this repo yet)
+**Skill count:** 76 builders / 76 reviewers / 100% paired
+**Open issues:** 12
+**Notes:** Label audit found the open set already well-typed: #3-#9, #15, #16 each carry a type (`description-quality`) plus a domain label; #10 and #11 carry `ci`. Only #12 (W22 dfmea-builder polish target) lacked a type label — its body is a frontmatter/description audit, so `description-quality` was added with high confidence. #10 and #11 are repo-wide tooling (`ci`) with no applicable domain label; rather than force a <80%-confidence domain, both are left domain-less and flagged here for human awareness. No stale issues: every open issue was updated 2026-06-03 or later, so zero 30-day auto-triage comments were posted. The Fri/Sat issue-count mystery is resolved: GET /issues/17 returns 404, meaning the CN-language discussion issue was deleted or spam-filtered at the GitHub level (not merely closed) — external action, nothing for the bot to do. STATUS regen reproduced the canonical domain spread (safety=15, quality=10) using the same inline 9-entry explicit map as Sat — ninth consecutive run of hand-maintained inline classification; #10 remains the fix.
+**Follow-ups:**
+- Mon W24 PLAN: land `scripts/classify_skill.py` (#10) — ninth inline regen this run; the explicit map is stable at 9 entries, ready to freeze.
+- Mon W24 PLAN: convert #4 (cs-concept) and #5 (aspice-assessment) from polish loops to maintainer-PR targets per Thu/Fri/Sat journals.
+- Mon W24 PLAN: include one SOTIF target (sotif-analysis or triggering-conditions) — zero-touch domain in May.
+- #11 (packaging utility, external patch attached) needs a human decision — it's been open since 2026-05-22 with a ready patch; bot policy is not to merge external code.
+- Fmeda medium findings (classification-ladder branch, SMvDU acronym, 100x unit convention) still await maintainer action.
+
+## 2026-06-08 (autonomous run, PLAN)
+
+**Mode:** PLAN
+**Action:** W24 plan written (docs/weekly/WEEK-2026-W24.md), 5 fresh tracking issues created (#19–#23), STATUS.md regenerated.
+**Files touched:** STATUS.md, docs/weekly/WEEK-2026-W24.md, docs/AUTONOMOUS_LOG.md (this entry)
+**Tests:** N/A (no test suite in this repo yet)
+**Skill count:** 76 builders / 76 reviewers / 100% paired
+**Open issues:** 5 (all created this run; tracker was at 0 on entry)
+**Notes:** The headline event is an external tracker reset — Sunday's TRIAGE recorded 12 open issues, but this morning the GitHub API returns `open_issues_count = 0`: a maintainer closed the entire backlog (#3–#12, #15, #16) over the weekend, including the four-week carryovers #4 (cs-concept) and #5 (aspice-assessment), tooling #10/#11. Judgement calls: (1) With no open issues, the standup priority order falls through (a) "issue-referenced skills" to (c) least-recently-touched builders; I picked for maximum domain spread across the stale 🟡 cohort (sotif/safety/quality/comms) plus one tooling slot. (2) I deliberately did NOT re-enqueue #4/#5 as polish loops — three weeks of journals recommended converting them to maintainer-PR targets, and the human closing them is read as a decision to end the loop, not reopen it; their ready rewrites stay in the polish log for a future maintainer PR. (3) SOTIF mandate honored (#20) — May's only zero-touch domain. (4) Classifier extraction re-filed fresh as #19 (successor to closed #10); the inline override map is stable at 9 entries and ready to freeze — this would otherwise be the 10th consecutive hand-maintained regen. (5) Issue numbers jumped to #19–#23 (tracker had passed #13/#14/#17/#18 via external activity). STATUS regen reproduced the canonical spread (safety=15, quality=10); only the two date lines changed vs. yesterday.
+**Follow-ups:**
+- Tue W24 POLISH: prioritize #19 (scripts/classify_skill.py) — highest-value debt retirement; explicit map is frozen at 9 entries and documented in the issue body. After it lands, every future STATUS regen is `python scripts/classify_skill.py > STATUS.md`.
+- Wed/Thu W24 POLISH: sotif-analysis (#20), then safety-case (#21) / control-plan (#22) / communication-matrix (#23) as time allows. Expect ~3 of 4 skill targets to land in-week.
+- Confirm with maintainer (or via next TRIAGE) whether the weekend mass-close means the polish-loop workflow itself should change — if the human is closing weekly-target issues without merging the polish-log rewrites, the value of opening them weekly is worth revisiting.
+- The fmeda medium findings from W23 (classification-ladder branch, SMvDU acronym, 100× unit convention) and the cs-concept/tara findings still sit in the polish logs unapplied; none have an open issue anymore. Flag for human: decide whether these become PRs or are dropped.
+
+## 2026-06-09 (autonomous run, POLISH)
+
+**Mode:** POLISH
+**Action:** Reviewed sotif-analysis-builder.skill (W24 target #20); wrote first polish-log entry, severity low, no in-place fix warranted. Regenerated STATUS.md.
+**Files touched:** docs/skill-polish-log/sotif-analysis-builder.md (new), STATUS.md, docs/AUTONOMOUS_LOG.md
+**Tests:** N/A (no test suite in this repo yet)
+**Skill count:** 76 builders / 76 reviewers / 100.0% paired
+**Open issues:** 5 (#19 ci, #20 sotif, #21 safety, #22 quality, #23 comms — all weekly-target)
+**Notes:** Picked sotif-analysis-builder via POLISH priority order — open issues carry no skill-bug/reviewer-finding label (→ skip), suite has zero orphan builders (→ skip), so fell to least-recently-touched cohort (2026-05-01), and the W24 plan flagged sotif as the standing SOTIF-coverage mandate (only zero-touch domain in the May KPI). Deliberately did NOT take the Tuesday tooling slot #19 (classify_skill.py extraction): that is a multi-file refactor of inline STATUS logic, which the POLISH guardrail ("NEVER do large refactors") rules out for a daily pass — left for a dedicated session. Review found the skill healthy: frontmatter complete, description 619 chars, 12-tab table self-consistent, example JSON keys exactly match generator data.get() fields, both scripts parse, no TODO/placeholder markers. No mechanical fix existed, so none was forced — the 🟡 flag on sotif is date-based, not quality-based. Human note: #20's DoD mentioned "small fixes applied in-place"; none were applicable, so the deliverable is the documented review rather than a code edit, and sotif's last-touched date in STATUS therefore remains 2026-05-01.
+**Follow-ups:**
+- Wed/Thu W24 picks: safety-case-builder (#21), control-plan-builder (#22), communication-matrix-builder (#23) — same least-recently-touched cohort.
+- Tooling debt #19 (classify_skill.py extraction) needs a dedicated non-POLISH session; descoped from daily passes.
+- Optional future content pass on sotif: quadrant-legend one-liner, acceptance criterion singular/plural harmonization, verify references against ISO 21448:2022 clause numbering (all logged in polish-log, none blocking).

docs/skill-polish-log/sotif-analysis-builder.md

@@ -0,0 +1,56 @@
+# Polish log — sotif-analysis-builder
+
+## 2026-06-09 (W24 POLISH, first pass)
+
+**Tracking issue:** #20 (W24 polish target, label `sotif`)
+**Mode:** POLISH · **Severity:** low (no blocking issues found)
+**In-place fix applied:** none required (see rationale)
+
+### What's good
+- **Frontmatter is valid and complete.** Required fields `name` and `description`
+  both present; `description` is 619 chars, comfortably under the 1024-char ceiling.
+  The description correctly frames SOTIF as distinct from ISO 26262 random-HW faults,
+  which is the single most important triggering distinction for this skill.
+- **Body is coherent and self-consistent.** The "Output structure (12 tabs)" header
+  matches the table exactly (rows 00–11 = 12 tabs). The tab inventory in the body
+  lines up with the tab list implied by the description.
+- **Schema/example/generator are aligned.** Example input
+  `examples/sample_sotif_input_aeb.json` has top-level keys
+  `[system, functions, odd_definition, performance_limitations,
+  functional_insufficiencies, triggering_conditions, hazardous_behaviors,
+  scenarios, acceptance_criteria]` and every one is consumed by
+  `scripts/generate_sotif_analysis.py` via a matching `data.get(...)`. No orphan
+  fields, no fields the generator reads that the example omits.
+- **Scripts are syntactically sound.** `generate_sotif_analysis.py` and `recalc.py`
+  both parse without error. No `TODO`/`FIXME`/`placeholder`/`lorem` markers anywhere
+  in the archive.
+- **Correct cross-reference.** "When to use" routes random-HW-failure hazards to
+  hara-builder, reinforcing the SOTIF-vs-FuSa boundary.
+
+### What to fix
+- Nothing blocking. The skill is in good health.
+
+### Suggested (non-blocking) edits for a future pass
+- **Quadrant terminology consistency (cosmetic):** the body uses both the standard
+  ISO 21448 4-quadrant labels and the prose "Known/Unknown × Safe/Unsafe". These
+  agree, but a one-line legend near tab 09 would remove any ambiguity for new users.
+- **Acceptance-criterion singular/plural:** prose refers to "Acceptance criterion"
+  (tab 10) while the input key is `acceptance_criteria` (plural). The generator
+  already keys on the plural, so this is purely descriptive — worth a one-word
+  harmonization only if the file is opened for another reason.
+- **Reference freshness:** `references/iso21448_clauses.md` cites the §6 concept /
+  §5 scenario taxonomy structure; confirm against the current ISO 21448:2022 clause
+  numbering on a future content pass (low priority — structure is unchanged).
+
+### Rationale for no in-place change
+Per POLISH discipline, edits are limited to small, obvious, unambiguous fixes
+(typo, over-length description, missing required frontmatter). None of those
+conditions are present here. The suggestions above are content-judgement calls,
+not mechanical fixes, so they are logged for a future deliberate pass rather than
+applied blind. A small honest commit beats a wrong one.
+
+### Net assessment
+Healthy skill. The 🟡 staleness flag in STATUS.md is **date-based, not
+quality-based** — the file simply hasn't been edited since 2026-05-01. This review
+satisfies the standing SOTIF-coverage mandate (SOTIF was the only zero-touch domain
+in the May KPI); the domain has now had a documented quality pass.

docs/weekly/WEEK-2026-W24.md

@@ -0,0 +1,80 @@
+# Week 2026-W24 — Plan
+
+_Auto-generated 2026-06-08 by automotive-skills-daily-standup (PLAN run)._
+
+## Recap — past 7 days
+
+```
+d8b19ef auto(triage): label refresh, #12 typed, #17 delta confirmed, STATUS regen
+8e826bb auto(release): v2026.06.W23 weekly snapshot, RELEASES.md, CHANGELOG roll, STATUS regen
+c21a84a auto(docs): W23 changelog roll, 3 example stubs, STATUS regen
+d6afa26 auto(polish): W23 #3 fmeda-builder pass, regen STATUS, journal
+22d6409 auto(polish): W23 #2 tara-builder pass, regen STATUS, journal
+5b4b006 auto(polish): W23 #1 cs-concept-builder pass, regen STATUS, journal
+f8e940f auto(monthly): KPI report for May 2026
+3af1f6b auto(plan): W23 targets — cs-concept, aspice-assessment, classifier, fmeda, tara
+```
+
+W23 closed clean: tag `v2026.06.W23` pushed, RELEASES.md drafted for manual
+Publish, 100% paired ratio (76/76) held. Three W23 polish passes landed
+(cs-concept, tara, fmeda) plus 3 example stubs and the May monthly KPI.
+
+**Tracker reset.** Sunday's TRIAGE recorded 12 open issues. As of this
+PLAN run the GitHub API reports `open_issues_count = 0` — **a maintainer
+closed every open issue** (#3–#12, #15, #16) between Sun and Mon. This
+clears the entire backlog the prior PLAN/POLISH cadence was anchored on,
+including the four-week carryovers #4 (cs-concept) and #5 (aspice-assessment)
+and the tooling debt #10 (classifier) and #11 (packaging utility). The
+standup priority order therefore falls through (a) "skills referenced by
+open issues" → none → to (c) least-recently-touched builders, with the
+standing journal mandates (SOTIF coverage, classifier extraction) folded in.
+
+## W24 targets
+
+Suite is 100% paired (76/76), zero orphan builders. With the issue tracker
+emptied, targets are drawn from the stale 🟡 cohort (74 builders untouched
+since 2026-05-01/02) for maximum domain spread, plus one tooling slot to
+finally retire the long-running inline-classifier debt. Fresh issues
+created this run; the human-closed carryovers (#4/#5) are deliberately
+**not** re-enqueued as polish loops (see Notes).
+
+| # | Target | Domain | Tracking issue | Definition of done |
+|---|---|---|---|---|
+| 1 | scripts/classify_skill.py extraction | tooling | #19 (successor to closed #10) | Extract inline STATUS-regen logic (domain inference + alias map + flag rules + 9-entry explicit override) into `scripts/classify_skill.py`; standup regenerates via `python scripts/classify_skill.py > STATUS.md`. DoD: output byte-matches current canonical spread; STATUS section of standup shrinks to one shell line. |
+| 2 | sotif-analysis-builder.skill | sotif | #20 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Satisfies the standing SOTIF-coverage mandate (only zero-touch domain in May KPI). |
+| 3 | safety-case-builder.skill | safety | #21 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. ISO 26262-2 capstone integrator, densest domain, never polished. |
+| 4 | control-plan-builder.skill | quality | #22 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Quality-domain anchor (AIAG Control Plan), stale since 2026-05-01. |
+| 5 | communication-matrix-builder.skill | comms | #23 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Central comms artifact, stale since 2026-05-02. |
+
+All five tracking issues were created fresh this run (#19–#23); the issue
+tracker had jumped past #13/#14/#17/#18 from external activity, consistent
+with prior journal notes.
+
+## Domain-spread check
+
+Targets span 4 distinct skill domains plus tooling: sotif (×1), safety (×1),
+quality (×1), comms (×1), tooling (×1). No domain is doubled — a deliberate
+spread across the stale cohort. Polish passes land Tue/Wed/Thu, so expect
+~3 of the 4 skill targets to execute in-week; the tooling slot (#19) is the
+priority Tuesday pick. Carryover lands on the W25 backlog.
+
+## Notes / judgement calls
+
+- **Do not re-enqueue #4/#5.** The four-week carryovers cs-concept (#4) and
+  aspice-assessment (#5) were closed by the maintainer this weekend along
+  with the rest of the backlog. Prior journals recommended converting them
+  to maintainer-PR targets; the human closing them is read here as a
+  decision to stop the polish loop, not an invitation to reopen it. Their
+  ready-to-apply rewrites remain in `docs/skill-polish-log/` for any future
+  maintainer PR. W24 picks fresh stale targets instead.
+- **Classifier extraction is now its own fresh issue (#19).** Closed #10
+  is its predecessor. This is the 10th run the inline map would otherwise be
+  hand-maintained; the explicit override is stable at 9 entries and ready to
+  freeze into `scripts/classify_skill.py`. Prioritized as the Tuesday slot.
+- **SOTIF mandate honored** via #20 (sotif-analysis-builder). May was the
+  only zero-touch SOTIF month per the monthly KPI; landing one SOTIF polish
+  in W24 prevents a second.
+- **Tag scheme** (a RELEASE concern, flagged four times in W23 journals)
+  resolved by default to ISO-absolute (`v2026.06.W23` shipped Saturday).
+  W24's Saturday RELEASE, if commits warrant, continues the ISO-absolute
+  series as `v2026.06.W24`. No further PLAN action.