Mediatools - #19

Fixes #332 (core gap + the six bundled nits from the #330 sweep reviews;
two of the six live in the blessed downstream reference and propagate
via the Vantage-Config carry, not this repo - see below).

## configure.sh: model inference on downstream carries

In a carry the registry is absent, so the no-arg form defaulted to
`release` and then hit the intended fail-safe abort on operational
carries (missing `develop.json`) - arg 2 was effectively mandatory
there. Now the model is inferred from which `develop` payload is carried
(a carry holds exactly its own model's); ambiguous layouts (both or
neither - e.g. a partial copy) abort rather than guess. Also: the model
may be passed as the sole argument (`configure.sh operational`) -
previously arg 1 was always parsed as a repo name (bundled nit,
Utilities #417).

Matrix-tested with the apply path stubbed: infer release, infer
operational, both-present abort (exit 1), neither-present abort (exit
1), explicit arg-2 override, model-as-sole-arg, unknown-model abort. Hub
behavior unchanged (registry present -> registry lookup, as before).
shellcheck + bash -n clean.

## Ruleset snippet hardening (duplicate-name id corruption)

The `id=$(gh api ... select(.name==...).id)` pattern in the README regen
snippet and AUDIT.md section 6 produced a **multiline id** when
duplicate same-name rulesets exist, silently corrupting the follow-up
API path (bundled nit, Utilities #417 + LanguageTags #278). Both
snippets now fetch the list once and enforce **exactly one** ruleset per
name: the regen snippet fails loudly (never regen from a guess); the
audit snippet reports `found N (defect/drift)` and continues - matching
the declared drift semantics. Live-tested read-only against this repo
(develop + main in sync; duplicate simulation counts correctly).

## README wording

Documents the inference fallback and the model-only argument form
(bundled nit, Utilities #417).

## Bundled nits NOT in this PR (with rationale)

- `gh api --input -` portability (MediaTools #19): declined - fleet
standard is current gh; not worth temp-file churn.
- jq-derived secret name lists + `--paginate` in the secrets check
(MediaTools #19, LanguageTags #278, PlexCleaner #854): these live in the
**blessed downstream self-audit reference** (the Vantage-Config carry),
not in hub files - propagated there directly after this merges (the
hub's fleet audit reads `spec/secrets.json` programmatically already).

## Propagation caveat

This re-drifts the five existing carries (Vantage-Config + the four #330
sweep repos) until their next conformance touch; Vantage-Config is
updated immediately after this merges since it is the blessed reference
the queued operational standups (HomeAssistant-Config #16,
ESPHome-Config #46, HomeAutomation-Config #21) will adapt from.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…try (#3923)

## Summary

Updates the DevKitCIoT registry entry for its standup to the fleet
standard (ptr727/DevKitCIoT#16 through #19, on DevKitCIoT `develop`).

- **Drops `pullRequestCheck: false`.** DevKitCIoT `develop` now carries
the `validate-task.yml` caller and its `Check pull request workflow
status job` aggregator. Once this reaches hub `main`,
`repo-config/configure.sh apply ptr727/DevKitCIoT release` adds the
required status check to both rulesets, ahead of the DevKitCIoT
promotion (ptr727/DevKitCIoT#20).
- **Adds `description`.** It matches DevKitCIoT's new README tagline, so
`configure.sh apply` writes the About panel.
- **Rewrites the three `driftNotes`.** They now describe the current CI,
the vendored part library, and the pending promotion, each saying which
branch it is true on.

## Verification

- `spec/validate.py` passes.
- The prose gate passes on the diff.
- Local strict review ran three recorded passes. Rounds 1 and 2
qualified two notes that were true only on DevKitCIoT `develop`.

Until the DevKitCIoT promotion merges, the audit reports `main`'s old
README tagline against the declared description. That clears at the
promotion, and the About panel clears at `apply`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

<!-- coderabbit-ai-generated:v1 -->

## Summary by CodeRabbit

* **Documentation**
* Updated the DevKitCIoT registry listing with a description of its
ESP32-DevKitC board.
* Revised project notes to describe the KiCad validation hook,
project-local parts library on `develop`, branch divergence, and planned
promotion to `main`.
  * The listing no longer marks pull request checks as disabled.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>