auto(plan): W23 targets — cs-concept, aspice-assessment, classifier, fmeda, tara

Autonomous daily run.
- Published docs/weekly/WEEK-2026-W23.md (3 polish + 1 tooling + 1 polish)
- Opened tracking issues #15 (fmeda-builder) and #16 (tara-builder)
- Promoted #10 (extract scripts/classify_skill.py) as W23 tooling slot
- Regen STATUS.md, journal entry

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

STATUS.md

@@ -1,6 +1,6 @@
 # STATUS — Automotive Skills Suite
 
-_Auto-regenerated by `automotive-skills-daily-standup` (2026-05-31 TRIAGE run)._
+_Auto-regenerated by `automotive-skills-daily-standup` (2026-06-01 PLAN run)._
 
 **Total builders:** 76 · **Total reviewers:** 76 · **Paired:** 76 (100%) · **Orphans:** 0
 

docs/AUTONOMOUS_LOG.md

@@ -350,3 +350,17 @@ Standout finding is non-DoD and more impactful than the trigger gaps: the SKILL.
 - Monday W23 PLAN run should pick targets from the stale 🟡 cohort (38 builders untouched in 30+ days)
 - Issue #11 (skill-packaging utility) and #10 (freeze classify_skill.py) are tooling tasks — consider promoting one of them as a W23 target
 - The classifier logic now embedded in this run should eventually be extracted to scripts/classify_skill.py per issue #10
+
+## 2026-06-01 (autonomous run, PLAN)
+
+**Mode:** PLAN
+**Action:** Published W23 plan with 5 targets (3 polish + 1 tooling + 1 polish): cs-concept and aspice-assessment as 4-week carryovers, scripts/classify_skill.py extraction as a long-overdue tooling slot, fmeda and tara as fresh stale-cohort picks. Opened issues #15 (fmeda) and #16 (tara); referenced existing issues #4, #5, #10 in place. Regenerated STATUS.md.
+**Files touched:** docs/weekly/WEEK-2026-W23.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% paired
+**Open issues:** 12 (was 10 — added #15, #16)
+**Notes:** First Monday of June. Two clean judgement calls. (1) Took the explicit advice from the W22 RELEASE and TRIAGE journal entries that cs-concept (#4) and aspice-assessment (#5) had to lead W23 — they have now slipped four consecutive weeks, longer than any other open polish issue. Leaving them un-prioritized again would have made the carryover unrecoverable. (2) Promoted #10 (extract scripts/classify_skill.py) into the W23 target list as the one tooling slot. Six consecutive standup runs have re-implemented the STATUS classifier inline; the alias map for ppap-package and item-definition is now data-driven within the inline helper but the helper itself is still ~50 lines copied each run. Without this extraction, the standup is one silent rule change away from drifting reviewer-pairing logic. Other note: when creating the two new issues the GitHub tracker returned #15 and #16 rather than the expected #13/#14 — the WEEK file was patched to match. The standup spec calls the release tag `vYYYY.MM.W<n>` with W = ISO week within current month; prior tags shipped as ISO-absolute (W20/W21/W22). Now that June starts, Sat RELEASE will hit this ambiguity head-on — flagging again so the human can call it on tag-cut day if not before.
+**Follow-ups:**
+- Tue/Wed/Thu POLISH runs (3 slots): in priority order pick targets #1 (cs-concept), #2 (aspice-assessment), then either #4 (fmeda) or #5 (tara). Target #3 (tooling) is fine to land on any POLISH day if time allows — it's a small refactor, not a per-skill audit.
+- Issues #11 (skill-packaging utility) and #7/#8 (W21 description-quality carryovers for dbc/autosar-swc) remain open but un-prioritized this week. If a future POLISH slot opens up, #11 is the higher-leverage tooling item.
+- W23 RELEASE (Sat 2026-06-06) needs a human ruling on tag scheme before tag-cut: `v2026.06.W23` (ISO-absolute, continuity) vs. `v2026.06.W1` (per-month, spec-literal). Default will be ISO-absolute unless the human says otherwise by Saturday.

docs/weekly/WEEK-2026-W23.md

@@ -0,0 +1,60 @@
+# Week 2026-W23 — Plan
+
+_Auto-generated 2026-06-01 by automotive-skills-daily-standup (PLAN run)._
+
+## Recap — past 7 days
+
+```
+f54a710 auto(triage): regen STATUS with alias-aware pairing, journal day
+3ec50a0 auto(release): v2026.05.W22 weekly snapshot, RELEASES.md, CHANGELOG roll, STATUS regen
+f9e63f9 auto(docs): W22 changelog roll-up, 3 example stubs, STATUS regen
+ef78172 auto(polish): W22 #2 hara-builder pass, regen STATUS, journal
+04482aa auto(polish): W22 #5 dfmea-builder pass, regen STATUS, journal
+9850780 auto(polish): W22 #1 uds-services-builder pass, regen STATUS
+973c075 auto(plan): W22 targets — uds, hara, cs-concept, aspice-assessment, dfmea
+```
+
+W22 closed clean: tag `v2026.05.W22` is pushed, RELEASES.md drafted for
+manual Publish, 100% paired ratio held. Three of five W22 polish targets
+landed in-week (uds, hara, dfmea); cs-concept (#4) and aspice-assessment (#5)
+slipped per the W22 docs/release journal entries. Both are W20-originated
+issues now in their fourth consecutive week of carryover — they MUST lead
+W23 to stop the bleed.
+
+## W23 targets
+
+Suite remains 100% paired (76 / 76), no orphan builders to chase. Priority
+order applied: (a) skills referenced by oldest open issues, (b) one tooling
+slot to retire the longest-open infra debt (#10 classifier freeze), (c) a
+fresh stale-cohort pick to keep the polish wheel turning.
+
+| # | Target | Domain | Tracking issue | Definition of done |
+|---|---|---|---|---|
+| 1 | cs-concept-builder.skill | cyber | #4 (4-week carryover) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited against current archive; small obvious fixes applied in-place; severity logged. |
+| 2 | aspice-assessment-builder.skill | aspice | #5 (4-week carryover) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. |
+| 3 | scripts/classify_skill.py extraction | tooling | #10 (6-run carryover) | Extract the inline STATUS-regen Python (domain inference + alias map + flag rules) into `scripts/classify_skill.py`; daily standup invokes it via `python scripts/classify_skill.py > STATUS.md`. DoD: standup STATUS section shrinks to one shell line. |
+| 4 | fmeda-builder.skill | safety | #15 (new) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Picked from stale 🟡 cohort (untouched since 2026-05-01) — densest safety-domain builder still un-polished. |
+| 5 | tara-builder.skill | cyber | #16 (new) | Fresh W23-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Cyber-domain anchor skill, stale since 2026-05-01. |
+
+Two existing issues (#4, #5) are referenced in place rather than duplicated
+— consistent with W22 plan precedent. Two fresh issues (#15, #16) created
+for the new polish targets (issue tracker had jumped past #13/#14 between W22 close and this PLAN run). One existing issue (#10) elevated as the W23
+tooling slot.
+
+## Domain-spread check
+
+Targets span 4 distinct domains plus tooling: cyber (×2), aspice (×1),
+safety (×1), tooling (×1). Polish runs land Tue/Wed/Thu so expect ~3 of
+these 5 to execute this week; carryover lands on W24 backlog.
+
+## Notes / judgement calls
+
+- The standup spec literally reads `vYYYY.MM.W<n>` with W = "ISO week within
+  current month". Prior tags (W20/W21/W22) used ISO-absolute week numbers
+  for continuity. June 1 starts a new month — if W23 RELEASE keeps the
+  ISO-absolute scheme the tag is `v2026.06.W23`; if it switches it becomes
+  `v2026.06.W1`. Flagged for human direction; PLAN does not decide.
+- W22 RELEASE journal flagged that the alias map for ppap-package and
+  item-definition pairing is now data-driven inside the inline helper.
+  Target #3 (scripts/classify_skill.py) will lift it into a real
+  repo-versioned tool so future runs do not silently drift.