repo-layout

# ult-repo-layout (Frontmatter `name:` is the bare `repo-layout` — `ult` is this skill's `namespace:`, composed into the folder name and every invocation below. Same pattern elsewhere in this repo, e.g. `sec-threat-model`'s `name:` is `threat-model`.) This skill implements the project layout and path-dependency configuration model (§15) and workspace-root consolidation (§16 — `layout.workspace_root`, scaffold-not-copy, and the `layout-slots-registry.yaml` superset registry), covering **eight** path-slots: - `context_packages` — read/written by `ult-context-generate` and every `CONSUMING-CONTEXT-PACKAGE.md` consumer. The only slot a real, shipped skill in this repo both produces and consumes. - `compiled_guidelines` — written by `compiling-project-guidelines`, read by its own `CONSUMING-COMPILED-GUIDELINES.md` consumers. The registry's only `kind: file` slot, and the only slot whose D21 default re-roots to a different bucket (`inputs` → `cache`). - `plans_output`, `brainstorm_output`, `user_stories_output`, `security_docs`, `security_report`, `project_plan_docs` — six further slots, all **illustrative — not shipped in this repo** (see the slot registry table below; rationale in `references/phase-history.md`). ...plus the **`project_guidelines` starter-kit drop-zone** — not a `project_layout` path-slot (no marker, no resolution algorithm), just a regenerated `.pointer.md` scaffold file. Read `references/starter-kit-dropzones.md` now and follow it if you're t...