P0: the skeleton and the fleet's quality gate, from the first pull request #2

The repository gets its skeleton and the quality gate of the fleet, both in place from its first pull request.

Caller

• platform#1, slice P0 and invariant 6: the fleet's quality gate holds from the first pull request.
• The operator, hal head chat, 06.11.2026, on creating this repository: „beim anlegen gleich alles wichtige aus quality von anfang an rein?“

What it holds

• README.md, for the operator. It says what the repository is and is not, from the target picture of Platform on k3s and Flux: from an empty PC to every app live, with hal archived #1, in short, linking Platform on k3s and Flux: from an empty PC to every app live, with hal archived #1 for the plan. It holds no plans and no status. It opens with the guiding sentence of Platform on k3s and Flux: from an empty PC to every app live, with hal archived #1, word for word, which the operator blessed on 06.11.2026.
• AGENTS.md, with only what holds here alone: commands, layout and owners. CLAUDE.md is exactly @AGENTS.md.
• The gate, at quality v0.9.2 (07bdf7c478ac9cc9cd348b180abd3cbc9d873f23), the release hal, hopin and speech-runtime pin today:
  • a CI workflow whose quality job calls quality's gate.yml;
  • one mandatory job beside it, checks, the job later slices extend (P3 adds the manifest render and schema checks). In P0 it runs one real check over what the repository holds that the gate does not already run; no placeholder step. The pull request names the check and why;
  • quality/config.toml, naming the mandatory jobs and every root entry outside quality's base list;
  • sonar-project.properties.
• CodeQL through quality's reusable codeql.yml for the language actions, as marketplace, aco and quality call it. The repository is public, so it costs nothing, and its code will be mostly workflows and manifests.
• Dependabot for GitHub Actions only, since no other ecosystem exists yet.
• No manifests and no product code. They start in P1 to P3.

How each line looks is owned by quality: its README, docs/gate.md, docs/sonar.md and docs/rules.md. Read them at that release with git -C ~/git/quality show v0.9.2:<path>. Copy no snippet from hal or another app.

Outside the diff

• SonarCloud. The project overnightworks_platform exists (public API, no analysis yet). Whether its automatic analysis is off is unverified; if the first run reports it on, the head asks the operator for that one click. The organisation secret SONAR_TOKEN already reaches every repository.
• The required check. The organisation ruleset requires quality / verdict on the default branch of every repository whose custom property quality_gate is true (quality docs/gate.md). It is false here today. Once the first run has reported quality / verdict, the head sets it to true, or asks the operator if the setting is refused. No branch protection or repository ruleset of its own.

version = 1
now = "Opened 06.11.2026 by hal's head as P0 of #1; pulled 06.11.2026 by platform's head, who added the CodeQL caller and named the quality_gate property as the required-check mechanism."
next = "Build the skeleton at quality v0.9.2 and run it through review, CI and landing."
done_when = "A pull request carrying README.md, AGENTS.md, CLAUDE.md, the CI workflow with the gate caller and the checks job, the CodeQL caller, quality/config.toml, sonar-project.properties and Dependabot passes quality / verdict and CodeQL; main requires quality / verdict through quality_gate=true; quality hygiene at v0.9.2 prints hygiene: clean."
size = "S"
scope = ["README.md", "AGENTS.md", "CLAUDE.md", ".github", "quality", "sonar-project.properties", ".gitignore"]
whole = "The skeleton's files work only together: one gate run reads the workflow, its config and the Sonar properties at once."