.claude/rules/credential-routing.md

@@ -1,50 +0,0 @@
-# Credential and access routing
-
-**Audience:** Codex, Claude Code, Grok, and custodian agents that call **llm-connect**
-for inference. Run this check **before** requesting secrets, API keys, SSH access,
-login tokens, or database passwords — in any repo, not only `ops-warden`.
-
-ops-warden **issues SSH certificates only** (`warden sign`, `cert_command`). Every
-other credential need belongs to another subsystem. **Do not** message
-`ops-warden` on State Hub expecting a secret value; the reply is a pointer, not a key.
-
-### Lookup (do this first)
-
-```bash
-warden route find "<describe your need>" --json
-warden route show <catalog-id> --json
-```
-
-Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run warden`).
-
-| Agent runtime | How to orient |
-| --- | --- |
-| **Codex / Grok** (shell, HTTP State Hub) | `warden route` commands above; inbox `to_agent=vergabe-teilnahme` is for coordination, not secret vending |
-| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workstreams; **still** use `warden route` for credential ownership |
-| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody to OpenBao/operator paths surfaced by `warden route` |
-
-### Quick routing table
-
-| I need… | Owner | ops-warden executes? |
-| --- | --- | --- |
-| SSH cert (`adm`/`agt`/`atm`) | ops-warden | **Yes** — `warden sign` |
-| API key, DB password, provider token | OpenBao (`railiance-platform`) | No — route only |
-| Login / OIDC / MFA | key-cape / Keycloak | No — route only |
-| Authorization decision | flex-auth | No — route only |
-| activity-core → issue-core emission | activity-core + issue-core | No — `warden route show activity-core-issue-sink` |
-| SSH tunnel | ops-bridge (+ `cert_command` from warden) | No — route only |
-
-### Anti-patterns (do not do these)
-
-- `POST /messages/` to `ops-warden` asking for `ISSUE_CORE_API_KEY`, `OPENROUTER_API_KEY`, etc.
-- Inventing `warden secret`, `warden login`, `warden bao`, `warden tunnel` — they do not exist
-- Pasting secrets into Git, State Hub, workplans, logs, or chat
-
-### Other capabilities (reuse-surface)
-
-Non-credential capabilities are usually discovered through **reuse-surface** federation
-(`reuse-surface` registry / `capability.*` indexes). Credential routing is inlined in
-every repo's agent instructions because it is high-frequency, high-risk, and easy to
-get wrong.
-
-**Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`

.claude/rules/first-session.md

@@ -1,11 +1,11 @@
 ## First Session Protocol
 
-Triggered when `get_domain_summary("communication")` shows **no workstreams**.
+Triggered when `get_domain_summary("vergabe_teilnahme")` shows **no workstreams**.
 The project is registered but work has not yet been structured.
 
 **Step 1 — Read, don't write**
-- `~/the-custodian/canon/projects/communication/project_charter_v0.1.md` — purpose, scope
+- `~/the-custodian/canon/projects/vergabe_teilnahme/project_charter_v0.1.md` — purpose, scope
-- `~/the-custodian/canon/projects/communication/roadmap_v0.1.md` — planned phases
+- `~/the-custodian/canon/projects/vergabe_teilnahme/roadmap_v0.1.md` — planned phases
 - Scan repo root: README, directory structure, existing code or docs
 
 **Step 2 — Survey in-progress work**
@@ -17,20 +17,20 @@ roadmap phase. **Wait for approval before creating.**
 
 **Step 4 — Create workplan file first, then DB record (ADR-001)**
 ```
-workplans/WP-NNNN-<slug>.md   ← write this first
+workplans/vergabe_teilnahme-WP-NNNN-<slug>.md   ← write this first
 ```
 Then register in the hub:
 ```
-create_workstream(topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", title="...", owner="...", description="...")
+create_workstream(topic_id="7d4d3e35-312f-4723-bde9-ddb43799109e", title="...", owner="...", description="...")
 create_task(workstream_id="<id>", title="...", priority="high|medium|low")
 ```
 
 **Step 5 — Record the setup**
 ```
 add_progress_event(
-    summary="First session: structured communication into N workstreams, M tasks",
+    summary="First session: structured vergabe_teilnahme into N workstreams, M tasks",
     event_type="milestone",
-    topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc",
+    topic_id="7d4d3e35-312f-4723-bde9-ddb43799109e",
     detail={"workstreams": [...], "tasks_created": M}
 )
 ```

.claude/rules/repo-identity.md

@@ -1,5 +1,5 @@
-**Purpose:** Coulomb project repository (bootstrapped from repo-seed template)
+**Purpose:** Django 6 + Tailwind + HTMX bid management app
 
-**Domain:** communication
+**Domain:** vergabe_teilnahme
-**Repo slug:** vergabe-teilnahme
+**Repo slug:** vergabe_teilnahme
-**Topic ID:** 36c7421b-c537-4723-bf75-42a3ebc6a1dc
+**Topic ID:** 7d4d3e35-312f-4723-bde9-ddb43799109e

.claude/rules/session-protocol.md

@@ -1,7 +1,6 @@
 ## Session Protocol
 
-Dev Hub (State Hub API): http://127.0.0.1:8000
+State Hub: http://127.0.0.1:8000
-MCP server name in `~/.claude.json`: `dev-hub`
 
 **Step 1 — Orient**
 
@@ -11,7 +10,7 @@ cat .custodian-brief.md
 ```
 Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
 ```
-get_domain_summary("communication")
+get_domain_summary("vergabe_teilnahme")
 ```
 If MCP tools are unavailable in the current agent session, use the REST API:
 ```bash
@@ -22,14 +21,14 @@ If the hub is offline: `cd ~/state-hub && make api`
 **Step 2 — Check inbox**
 With MCP tools:
 ```
-get_messages(to_agent="vergabe-teilnahme", unread_only=True)
+get_messages(to_agent="vergabe_teilnahme", unread_only=True)
 ```
 Mark read with `mark_message_read(message_id)`. Reply or act on coordination
 requests before proceeding.
 
 Without MCP tools:
 ```bash
-curl -s "http://127.0.0.1:8000/messages/?to_agent=vergabe-teilnahme&unread_only=true" \
+curl -s "http://127.0.0.1:8000/messages/?to_agent=vergabe_teilnahme&unread_only=true" \
   | python3 -m json.tool
 curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
   -H "Content-Type: application/json" -d '{}'
@@ -40,12 +39,12 @@ curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
 ls workplans/
 ```
 For each file with `status: ready`, `active`, or `blocked`, note pending
-`wait`/`todo`/`progress` tasks.
+`todo`/`in_progress` tasks.
 
 **Step 4 — Present brief**
 
-1. **Active workstreams** for `communication` — title, task counts, blocking decisions
+1. **Active workstreams** for `vergabe_teilnahme` — title, task counts, blocking decisions
-2. **Pending tasks** from `workplans/` + any `[repo:vergabe-teilnahme]` hub tasks
+2. **Pending tasks** from `workplans/` + any `[repo:vergabe_teilnahme]` hub tasks
 3. **Goal guidance** — if `goal_guidance` in summary:
    - `needs_workplan`: surface as top action — *"Repo goal '{title}' has no workplan yet"*
    - `alignment_warnings`: flag if active work is not aligned with current goal
@@ -62,23 +61,23 @@ If no workstreams: follow First Session Protocol (`first-session.md`).
 **Session close:**
 With MCP tools:
 ```
-add_progress_event(summary="...", topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", workstream_id="<uuid>")
+add_progress_event(summary="...", topic_id="7d4d3e35-312f-4723-bde9-ddb43799109e", workstream_id="<uuid>")
 ```
 Without MCP tools:
 ```bash
 curl -s -X POST http://127.0.0.1:8000/progress/ \
   -H "Content-Type: application/json" \
-  -d '{"topic_id":"36c7421b-c537-4723-bf75-42a3ebc6a1dc","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
+  -d '{"topic_id":"7d4d3e35-312f-4723-bde9-ddb43799109e","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
 ```
 If workplan files were modified, ensure the local copy is up to date first:
 ```bash
 git -C <repo_path> pull --ff-only
-cd ~/state-hub && make fix-consistency REPO=vergabe-teilnahme
+cd ~/state-hub && make fix-consistency REPO=vergabe_teilnahme
 ```
 For repos where implementation runs on a remote machine (e.g. CoulombCore),
 use the combined target which pulls before fixing:
 ```bash
-cd ~/state-hub && make fix-consistency-remote REPO=vergabe-teilnahme
+cd ~/state-hub && make fix-consistency-remote REPO=vergabe_teilnahme
 ```
 **C-15** (DB task ahead of file) is normal in multi-machine workflows — writeback
 will sync the file to match DB.  **C-16** (repo behind remote) blocks all writes

.claude/rules/workplan-convention.md

@@ -1,7 +1,7 @@
 ## Workplan Convention (ADR-001)
 
-File location: `workplans/WP-NNNN-<slug>.md`
+File location: `workplans/vergabe_teilnahme-WP-NNNN-<slug>.md`
-ID prefix: `WP-`
+ID prefix: `VERGABE_TEILNAHME-WP`
 
 Work items originate as files in this repo **before** being registered in the hub.
 
@@ -12,7 +12,7 @@ repo state, and `finished` when implementation is complete. `stalled` and
 `needs_review` are derived health labels, not stored statuses.
 
 Closed workplans may be moved to `workplans/archived/` with a completion-date
-prefix: `YYMMDD-WP-NNNN-<slug>.md`. The frontmatter id remains
+prefix: `YYMMDD-vergabe_teilnahme-WP-NNNN-<slug>.md`. The frontmatter id remains
 unchanged; the prefix is only for quick visual reference.
 
 Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
@@ -21,20 +21,8 @@ Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**
 directly. Promote anything requiring analysis, design, approval, dependencies, or
 multiple planned phases into a normal workplan.
 
-Ecosystem todos from other agents arrive as `[repo:vergabe-teilnahme]` hub tasks —
+Ecosystem todos from other agents arrive as `[repo:vergabe_teilnahme]` hub tasks —
 visible at session start. Pick one up by creating the workplan file, then registering
 the workstream.
 
-Task blocks use this shape:
-
-```task
-id: WP-NNNN-T01
-status: wait | todo | progress | done | cancel
-priority: high | medium | low
-state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
-```
-
-Status progression is `todo` → `progress` → `done`; use `wait` for waiting or
-blocked work and `cancel` for stopped work.
-
 <!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->

.forgejo/workflows/ci-smoke.yaml

@@ -1,29 +0,0 @@
-# Canonical CI smoke template (tier 1 routing drill).
-# Copy to: .forgejo/workflows/ci-smoke.yaml in consumer repos.
-name: CI Smoke
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-jobs:
-  host-smoke:
-    runs-on: self-hosted
-    steps:
-      - name: Routing probe (host runner)
-        run: |
-          set -eu
-          echo "repository=${GITHUB_REPOSITORY:-unknown}"
-          echo "sha=${GITHUB_SHA:-unknown}"
-          echo "runner=${RUNNER_NAME:-unknown}"
-          uname -a
-
-  container-smoke:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Routing probe (container label)
-        run: |
-          set -eu
-          echo "container-smoke ok for ${GITHUB_REPOSITORY:-unknown}"

.repo-classification.yaml

@@ -1,19 +0,0 @@
-repo_classification:
-  standard: Repo Classification Standard
-  version: '1.0'
-  classified_at: '2026-06-22'
-  classified_by: agent
-  category: experimental
-  domain: communication
-  secondary_domains: []
-  capability_tags:
-  - marketplace
-  - collaboration
-  - procurement
-  - governance
-  business_stake:
-  - product
-  - sales
-  business_mechanics:
-  - coordination
-  - operation

AGENTS.md

@@ -2,12 +2,12 @@
 
 ## Repo Identity
 
-**Purpose:** Coulomb project repository (bootstrapped from repo-seed template)
+**Purpose:** Django 6 + Tailwind + HTMX bid management app
 
-**Domain:** communication
+**Domain:** vergabe_teilnahme
-**Repo slug:** vergabe-teilnahme
+**Repo slug:** vergabe_teilnahme
-**Topic ID:** `36c7421b-c537-4723-bf75-42a3ebc6a1dc`
+**Topic ID:** `7d4d3e35-312f-4723-bde9-ddb43799109e`
-**Workplan prefix:** `WP-`
+**Workplan prefix:** `VERGABE_TEILNAHME-WP-`
 
 ---
 
@@ -28,11 +28,11 @@ there is no MCP server for Codex agents.
 cat .custodian-brief.md
 
 # Active workstreams for this domain
-curl -s "http://127.0.0.1:8000/workstreams/?topic_id=36c7421b-c537-4723-bf75-42a3ebc6a1dc&status=active" \
+curl -s "http://127.0.0.1:8000/workstreams/?topic_id=7d4d3e35-312f-4723-bde9-ddb43799109e&status=active" \
   | python3 -m json.tool
 
 # Check inbox
-curl -s "http://127.0.0.1:8000/messages/?to_agent=vergabe-teilnahme&unread_only=true" \
+curl -s "http://127.0.0.1:8000/messages/?to_agent=vergabe_teilnahme&unread_only=true" \
   | python3 -m json.tool
 ```
 
@@ -63,8 +63,8 @@ Omit `workstream_id` / `task_id` when not applicable.
 ```bash
 curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
   -H "Content-Type: application/json" \
-  -d '{"status": "progress"}'
+  -d '{"status": "in_progress"}'
-# values: wait | todo | progress | done | cancel
+# values: todo | in_progress | done | blocked
 ```
 
 ### Flag a task for human review
@@ -81,9 +81,9 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 
 **Start:**
 1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
-2. Check inbox: `GET /messages/?to_agent=vergabe-teilnahme&unread_only=true`; mark read
+2. Check inbox: `GET /messages/?to_agent=vergabe_teilnahme&unread_only=true`; mark read
 3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
-4. Check human-needed tasks: `GET /tasks/?needs_human=true`
+4. Check blocked tasks: `GET /tasks/?needs_human=true`
 
 **During work:**
 - Update task statuses in workplan files as tasks progress
@@ -95,78 +95,21 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 3. Note for the custodian operator: after workplan file changes, run from
    `~/state-hub`:
    ```bash
-   make fix-consistency REPO=vergabe-teilnahme
+   make fix-consistency REPO=vergabe_teilnahme
    ```
    This syncs task status from files into the hub DB.
 
 ---
 
-## Credential and access routing
-
-**Audience:** Codex, Claude Code, Grok, and custodian agents that call **llm-connect**
-for inference. Run this check **before** requesting secrets, API keys, SSH access,
-login tokens, or database passwords — in any repo, not only `ops-warden`.
-
-ops-warden **issues SSH certificates only** (`warden sign`, `cert_command`). Every
-other credential need belongs to another subsystem. **Do not** message
-`ops-warden` on State Hub expecting a secret value; the reply is a pointer, not a key.
-
-### Lookup (do this first)
-
-```bash
-warden route find "<describe your need>" --json
-warden route show <catalog-id> --json
-```
-
-Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run warden`).
-
-| Agent runtime | How to orient |
-| --- | --- |
-| **Codex / Grok** (shell, HTTP State Hub) | `warden route` commands above; inbox `to_agent=vergabe-teilnahme` is for coordination, not secret vending |
-| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workstreams; **still** use `warden route` for credential ownership |
-| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody to OpenBao/operator paths surfaced by `warden route` |
-
-### Quick routing table
-
-| I need… | Owner | ops-warden executes? |
-| --- | --- | --- |
-| SSH cert (`adm`/`agt`/`atm`) | ops-warden | **Yes** — `warden sign` |
-| API key, DB password, provider token | OpenBao (`railiance-platform`) | No — route only |
-| Login / OIDC / MFA | key-cape / Keycloak | No — route only |
-| Authorization decision | flex-auth | No — route only |
-| activity-core → issue-core emission | activity-core + issue-core | No — `warden route show activity-core-issue-sink` |
-| SSH tunnel | ops-bridge (+ `cert_command` from warden) | No — route only |
-
-### Anti-patterns (do not do these)
-
-- `POST /messages/` to `ops-warden` asking for `ISSUE_CORE_API_KEY`, `OPENROUTER_API_KEY`, etc.
-- Inventing `warden secret`, `warden login`, `warden bao`, `warden tunnel` — they do not exist
-- Pasting secrets into Git, State Hub, workplans, logs, or chat
-
-### Other capabilities (reuse-surface)
-
-Non-credential capabilities are usually discovered through **reuse-surface** federation
-(`reuse-surface` registry / `capability.*` indexes). Credential routing is inlined in
-every repo's agent instructions because it is high-frequency, high-risk, and easy to
-get wrong.
-
-**Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`
-
-<!-- REPO-AGENTS-EXTENSIONS -->
-<!-- Append repo-specific agent instructions below this marker.
-     The state-hub template sync preserves content after this line. -->
-
----
-
 ## Workplan Convention (ADR-001)
 
 Work items originate as files in this repo — not in the hub. The hub is a
 read/cache/index layer that rebuilds from files.
 
-**File location:** `workplans/VERGABE-WP-NNNN-<slug>.md`
+**File location:** `workplans/VERGABE_TEILNAHME-WP-NNNN-<slug>.md`
 
 **Archived location:** finished workplans may move to
-`workplans/archived/YYMMDD-VERGABE-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
+`workplans/archived/YYMMDD-VERGABE_TEILNAHME-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
 the completion/archive date; the frontmatter `id` does not change.
 
 **Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@@ -178,11 +121,11 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 
 ```yaml
 ---
-id: VERGABE-WP-NNNN
+id: VERGABE_TEILNAHME-WP-NNNN
 type: workplan
 title: "..."
-domain: communication
+domain: vergabe_teilnahme
-repo: vergabe-teilnahme
+repo: vergabe_teilnahme
 status: proposed | ready | active | blocked | backlog | finished | archived
 owner: codex
 topic_slug: ...
@@ -202,8 +145,8 @@ derived health labels, not frontmatter statuses.
 ## Task Title
 
 ` ` `task
-id: VERGABE-WP-NNNN-T01
+id: VERGABE_TEILNAHME-WP-NNNN-T01
-status: wait | todo | progress | done | cancel
+status: todo | in_progress | done | blocked
 priority: high | medium | low
 state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 ` ` `
@@ -211,9 +154,9 @@ state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 Task description text.
 ```
 
-Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
+Status progression: `todo` → `in_progress` → `done` (or `blocked`)
 
 To create a new workplan:
 1. Write the file following the format above
-2. Notify the custodian operator to run `make fix-consistency REPO=vergabe-teilnahme`
+2. Notify the custodian operator to run `make fix-consistency REPO=vergabe_teilnahme`
    (or send a message to the hub agent via `POST /messages/`)

CLAUDE.md

@@ -8,5 +8,4 @@
 @.claude/rules/stack-and-commands.md
 @.claude/rules/architecture.md
 @.claude/rules/repo-boundary.md
-@.claude/rules/credential-routing.md
 @.claude/rules/agents.md

Makefile

@@ -1,4 +1,4 @@
-.PHONY: help db dev css seed migrate test lint shell superuser collectstatic sync-whynot-design
+.PHONY: help db dev css seed migrate test lint shell superuser collectstatic
 
 .DEFAULT_GOAL := help
 
@@ -41,6 +41,3 @@ shell: ## Open a Django shell (shell_plus if available)
 
 collectstatic: ## Collect static files into staticfiles/ (production step)
 	uv run manage.py collectstatic --noinput
-
-sync-whynot-design: ## Re-vendor whynot-design CSS+tokens from the pinned ref
-	./scripts/sync-whynot-design.sh

SCOPE.md

@@ -8,147 +8,130 @@
 
 ## One-liner
 
-Web application that structures a company's participation in tenders
+<!-- Describe the purpose of this repository in one precise sentence. -->
-(Ausschreibungen) end-to-end, from research through submission to
+<!-- Example: "Provides a lightweight event router for Kubernetes-native systems." -->
-post-award retrospective.
 
 ---
 
 ## Core Idea
 
-**Vergabe Teilnahme** ("tender participation") guides a team through the
+<!-- What is the main capability or idea behind this repository? -->
-full lifecycle of bidding on a public or private tender: collecting tender
+<!-- What problem does it try to solve? -->
-documents, analyzing requirements, deciding whether to participate, tracking
-open items, finalizing pricing and documents, submitting on time, and
-capturing reusable knowledge afterwards — win or lose. It is phase-guided,
-never phase-locked: every element of a tender is reachable at any time, and
-there is no forced completeness outside real submission-deadline
-constraints. All data entry is manual in this first build stage — no
-automated ingestion from tender platforms.
-
-It operates on three levels, per `wiki/ProductRequirementsDocument.md`:
-
-| Level | Content |
-|---|---|
-| Operational | deadlines, documents, tasks, lots (Lose), requirements, bidder questions, submission |
-| Management | participate/no-bid decision, approvals, pricing level, subcontractor selection, outcome, retrospective |
-| Strategic | reusable evidence/references, market price observation, loss reasons, win factors, competitor (Marktbegleiter) analysis |
 
 ---
 
 ## In Scope
 
-- Tender (Ausschreibung) and lot (Los) tracking through 8 navigable phases
+<!-- What this repository is responsible for. -->
-- Requirements analysis and bidder-question (Bieterfragen) handling
+<!-- Be explicit and concrete. -->
-- Task management (Aufgaben) scoped to a tender or a lot
+
-- Document management (Dokumente) for tender materials and submission artifacts
+-
-- Pricing (Preise) tracking per lot/tender
+-
-- Submission and post-award retrospective (Abgabe/Nachbetrachtung)
+-
-- Partner and reference library (Partner/Bibliothek) for reusable evidence
+
-- Competitor/market observation (Marktbegleiter)
+---
-- Feedback/bug capture within the app (Feedback)
-- Issue-tracking integration via `issue-core` (task facade, not a UI replacement)
 
 ## Out of Scope
 
-- External user accounts for partners/subcontractors/service providers (data
+<!-- What this repository deliberately does NOT do. -->
-  objects only in this build stage, no system access of their own)
+<!-- This is often more important than "In Scope". -->
-- Multi-tenancy
+
-- Automated ingestion from tender platforms, SharePoint, Teams, CRM, ERP,
+-
-  email, or calendars (deliberately manual-entry-first for v1)
+-
-- Certification or legal validity of submissions — the system tracks
+-
-  process state, it is not a legal compliance authority
 
 ---
 
 ## Relevant When
 
-- Deciding whether to bid on a tender and needing structured deadline,
+<!-- When should someone consider using or exploring this repository? -->
-  document, and requirement tracking across a team
+
-- Needing a system of record for pricing decisions, submission evidence,
+-
-  and post-award retrospectives on public/private tenders
+-
-- Wanting to reuse prior tender evidence, references, or competitor/pricing
+-
-  observations when evaluating a new tender
+
+---
 
 ## Not Relevant When
 
-- Needing external bidder/partner portal access (not built yet)
+<!-- When should someone ignore this repository? -->
-- Needing automated tender discovery or platform integration (out of scope
+
-  for this build stage)
+-
-- Needing generic project management unrelated to the tender-participation
+-
-  domain
+-
 
 ---
 
 ## Current State
 
-- Status: active
+<!-- Rough indication of maturity. No strict format required. -->
-- Implementation: substantial — 12 Django apps covering the full phase
+
-  model (accounts, aufgaben, ausschreibungen, bibliothek, core, dokumente,
+- Status: <!-- e.g. concept / experimental / active / stable / deprecated -->
-  feedback, lose, marktbegleiter, nachbetrachtung, partner, preise); 17
+- Implementation: <!-- e.g. idea / partial / substantial / complete -->
-  workplans (WP-0001–WP-0017) implemented in sequence from project
+- Stability: <!-- e.g. unstable / evolving / stable -->
-  scaffold through whynot-design token adoption
+- Usage: <!-- e.g. none / personal / internal / production -->
-- Stability: evolving — manual-entry-first v1; no CI workflow configured yet
+
-  (`.gitea/`/`.forgejo/` absent)
+<!-- Add any notes that help set expectations. -->
-- Usage: internal collaboration tool, not yet published for external use
 
 ---
 
 ## How It Fits
 
-- Upstream dependencies: `issue-core` (task-tracking facade, see
+<!-- Where does this repository sit in the bigger picture? -->
-  `vergabe_teilnahme/apps/aufgaben/issue_facade.py`), `whynot-design`
+
-  (visual language, vendored CSS/tokens)
+- Upstream dependencies:
-- Downstream consumers: none known
+- Downstream consumers:
-- Often used with: `railiance-apps` (deployment target per its own SCOPE.md,
+- Often used with:
-  which names `vergabe-teilnahme` as a user-facing service it deploys)
 
 ---
 
 ## Terminology
 
-- Preferred terms: Ausschreibung (tender), Los (lot), Aufgabe (task),
+<!-- Terms that are important to understand this repo. -->
-  Marktbegleiter (competitor/market companion), Nachbetrachtung (post-award
+<!-- Especially useful if naming differs from other repos. -->
-  retrospective)
+
-- Also known as: "Vergabe Teilnahme" (product name), "tender participation
+- Preferred terms:
-  management system" (English gloss)
+- Also known as:
-- Potentially confusing terms: "Partner" here means reference/subcontractor
+- Potentially confusing terms:
-  data objects, not system users
 
 ---
 
 ## Related / Overlapping Repositories
 
-- `issue-core` — task-tracking backend consumed via `issue_facade.py`
+<!-- List repositories that have similar or adjacent responsibilities. -->
-- `whynot-design` — visual language vendored into `static/src/vendor/`
+<!-- Helps detect duplication and navigate the ecosystem. -->
-- `railiance-apps` — deployment/workload layer for this service
+
+- <repo-name> — <!-- how it relates -->
 
 ---
 
 ## Getting Oriented
 
-- Start with: `wiki/ProductRequirementsDocument.md` (product intent, in
+<!-- If someone decides to look deeper, where should they start? -->
-  German), `wiki/ArchitectureBlueprint.md` (technology stack and design
+
-  principles)
+- Start with:
-- Key files / directories: `vergabe_teilnahme/apps/` (12 domain apps),
+- Key files / directories:
-  `vergabe_teilnahme/urls.py` (route map), `workplans/` (WP-0001–0017
+- Entry points:
-  build history)
-- Entry points: `manage.py runserver`; `vergabe_teilnahme/urls.py` maps
-  `/ausschreibungen/`, `/lose/`, `/aufgaben/`, `/dokumente/`, and more
 
 ---
 
 ## Provided Capabilities
 
-Registered in `registry/capabilities/capability.procurement.vergabe-teilnahme.md`
+<!-- What can this repo's domain provide to other domains on request? -->
-(reuse-surface federation; vector **D3/A1/C1/R1** after SCOPE.md fill-in and
+<!-- Each capability block is parsed by the state-hub capability catalog ingest. -->
-REUSE-WP-0017-T05 entry-2 review, 2026-07-07).
+<!-- Remove the examples and add your own, or leave empty if none. -->
+
+<!--
+```capability
+type: infrastructure
+title: Example capability title
+description: What this capability provides, in one or two sentences.
+keywords: [keyword1, keyword2, keyword3]
+```
+-->
 
 ---
 
 ## Notes
 
-Product and architecture documentation (`wiki/`) is in German; this SCOPE.md
+<!-- Anything else worth knowing. Keep it short. -->
-is in English per the reuse-surface registry's Markdown-first, agent-facing
-convention. Refer to `wiki/ProductRequirementsDocument.md` for the
-authoritative German-language product definition.

registry/README.md

@@ -1,12 +0,0 @@
-# Capability Registry
-
-Markdown-first capability index for federation and reuse planning.
-
-## Authoring
-
-1. Copy a capability entry template (see reuse-surface `templates/capability-entry.template.md`).
-2. Add the row to `indexes/capabilities.yaml`.
-3. Run `reuse-surface validate` from a checkout with the CLI installed.
-4. Merge to `main` and verify publish with `reuse-surface establish --publish-check`.
-
-Federation contract: reuse-surface `docs/RegistryFederation.md`.

registry/capabilities/capability.procurement.vergabe-teilnahme.md

@@ -1,147 +0,0 @@
----
-id: capability.procurement.vergabe-teilnahme
-name: Vergabe Teilnahme (Public Procurement Participation) Application
-summary: Django application (with a Vite/Tailwind frontend) for managing German public-procurement (Vergabe)
-  tender participation — Ausschreibungs- und Teilnahme-Management-System.
-owner: vergabe-teilnahme
-status: draft
-domain: communication
-tags:
-- procurement
-- django
-- vergabe
-maturity:
-  discovery:
-    current: D3
-    target: D4
-    confidence: medium
-    rationale: SCOPE.md filled 2026-07-07 with in/out scope, current state, terminology, and orientation
-      pointers; supported by wiki/ProductRequirementsDocument.md (German product definition) and
-      wiki/ArchitectureBlueprint.md. README.md remains a stale repo-seed leftover — SCOPE and wiki
-      are authoritative for discovery.
-  availability:
-    current: A1
-    target: A3
-    confidence: medium
-    rationale: Substantial Django application (12 domain apps, WP-0001–WP-0017 implemented) with
-      Vite/Tailwind frontend and docker-compose dev/test; SCOPE.md describes internal collaboration
-      use only — no hosted production deployment confirmed in this review.
-external_evidence:
-  completeness:
-    level: C1
-    confidence: medium
-    basis: scope_vs_intent_and_consumer_expectations
-    satisfied_expectations:
-    - in-scope/out-of-scope boundaries documented in SCOPE.md
-    - 8-phase tender participation model described with operational/management/strategic levels
-    - manual-entry-first v1 constraint and external-portal exclusion explicit
-    broken_expectations: []
-    out_of_scope_expectations: []
-  reliability:
-    level: R1
-    confidence: low
-    basis: consumer_quality_signals
-    known_reliability_risks:
-    - no CI workflow configured yet (per SCOPE.md current state)
-    - no production consumer telemetry (REUSE-WP-0019)
-    - README.md still stale repo-seed text — fix separately
-discovery:
-  intent: Guide a team through the full lifecycle of bidding on public or private tenders (Ausschreibungen)
-    — from research and participate/no-bid decisions through submission and post-award retrospective.
-  includes:
-  - tender (Ausschreibung) and lot (Los) tracking across 8 navigable phases
-  - requirements analysis and bidder-question (Bieterfragen) handling
-  - tasks (Aufgaben), documents (Dokumente), pricing (Preise), submission/retrospective (Abgabe/Nachbetrachtung)
-  - partner/reference library (Bibliothek) and competitor observation (Marktbegleiter)
-  - issue-core task facade integration (not a UI replacement)
-  excludes:
-  - external partner/subcontractor portal accounts (data objects only in v1)
-  - multi-tenancy
-  - automated ingestion from tender platforms, SharePoint, Teams, CRM, ERP, email, or calendars
-  assumptions: []
-  use_cases: []
-  research_memos: []
-availability:
-  current_level: A1
-  target_level: A3
-  current_artifacts:
-  - Django application (`vergabe_teilnahme`, 12 apps)
-  - Vite/Tailwind frontend (`static/`)
-  - docker-compose.dev.yml and docker-compose.test.yml
-  target_artifacts: []
-  consumption_modes:
-  - application (Django + Vite, local dev via docker-compose)
-relations:
-  depends_on:
-  - capability.infotech.issue-tracking
-  supports: []
-  related_to:
-  - capability.design.whynot-system
-evidence:
-  documentation:
-  - SCOPE.md
-  - wiki/ProductRequirementsDocument.md
-  - wiki/ArchitectureBlueprint.md
-  - pyproject.toml
-  tests:
-  - vergabe_teilnahme/apps/*/tests.py (pytest-django suite across domain apps)
-  - docker-compose.test.yml
-  consumer_feedback: []
-  bug_reports: []
-  incidents: []
-consumer_guidance:
-  recommended_for:
-  - teams needing structured German tender-participation workflow tracking (manual-entry-first v1)
-  - extending or deploying this specific Django application
-  not_recommended_for:
-  - automated tender-platform ingestion (out of scope for v1)
-  - external bidder/partner self-service portals (not built)
-  known_limitations:
-  - manual data entry only in v1 — no platform integration
-  - README.md is still repo-seed boilerplate; use SCOPE.md and wiki/ for orientation
-promotion_history:
-- date: "2026-07-07"
-  dimension: discovery
-  from: D1
-  to: D3
-  rationale: SCOPE.md filled with full in/out scope and current-state documentation (REUSE-WP-0017-T05 entry-2 review).
-  author: grok
-- date: "2026-07-07"
-  dimension: completeness
-  from: C0
-  to: C1
-  rationale: Consumer scope expectations now documented in SCOPE.md and wiki PRD.
-  author: grok
----
-
-# Vergabe Teilnahme (Public Procurement Participation) Application
-
-## Overview
-
-`vergabe-teilnahme` is a Django + Vite/Tailwind application for managing German public-procurement (Vergabe) tender participation end-to-end. SCOPE.md (filled 2026-07-07) documents the 8-phase, manual-entry-first v1 model across 12 Django apps.
-
-## Assessment notes
-
-### Discovery
-
-SCOPE.md now provides authoritative in/out scope, current state, terminology, and pointers to the German-language wiki PRD and architecture blueprint. Discovery promoted from D1 to D3; README cleanup remains a separate hygiene item.
-
-### Availability
-
-Substantial implemented application (WP-0001–WP-0017) with local docker-compose paths. Held at A1 until a hosted deployment path is confirmed (railiance-apps is named as deployment target in SCOPE.md).
-
-### Completeness
-
-Scope-vs-intent expectations are now documented (C1). Feature completeness against the full PRD is not independently verified in this review.
-
-### Reliability
-
-Pytest-django suite exists across domain apps (structural R1). No CI workflow or production telemetry yet.
-
-## Promotion checklist
-
-- [x] ID follows `capability.<domain>.<name>` pattern
-- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
-- [x] `external_evidence` is populated separately from `maturity`
-- [x] Relations reference valid capability IDs
-- [x] Index entry added in `registry/indexes/capabilities.yaml`

registry/indexes/capabilities.yaml

@@ -1,19 +0,0 @@
-version: 1
-updated: '2026-07-07'
-domain: helix_forge
-capabilities:
-- id: capability.procurement.vergabe-teilnahme
-  name: Vergabe Teilnahme (Public Procurement Participation) Application
-  summary: Django application (with a Vite/Tailwind frontend) for managing German public-procurement (Vergabe)
-    tender participation — Ausschreibungs- und Teilnahme-Management-System.
-  vector: D3 / A1 / C1 / R1
-  domain: communication
-  status: draft
-  owner: vergabe-teilnahme
-  path: registry/capabilities/capability.procurement.vergabe-teilnahme.md
-  tags:
-  - procurement
-  - django
-  - vergabe
-  consumption_modes:
-  - application (Django + Vite, local dev via docker-compose)

scripts/sync-whynot-design.sh

@@ -1,39 +0,0 @@
-#!/usr/bin/env bash
-# Synchronises the vendored copy of the whynot-design system from a pinned
-# upstream commit. Source: ~/whynot-design (worktree) or a clone from gitea.
-#
-# Usage: ./scripts/sync-whynot-design.sh [<commit-or-ref>]
-# Default: reads .whynot-design-ref from the vendor directory.
-#
-# See workplans/WP-0017-whynot-design-tokens.md for the adoption strategy.
-set -euo pipefail
-
-ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-VENDOR_DIR="$ROOT/static/src/vendor/whynot-design"
-REF_FILE="$VENDOR_DIR/.whynot-design-ref"
-SRC_REPO="${WHYNOT_DESIGN_SRC:-$HOME/whynot-design}"
-
-REF="${1:-}"
-if [[ -z "$REF" && -f "$REF_FILE" ]]; then
-  REF="$(cat "$REF_FILE")"
-fi
-if [[ -z "$REF" ]]; then
-  echo "Usage: $0 <commit-or-ref>   (or write a ref to $REF_FILE)" >&2
-  exit 2
-fi
-
-if [[ ! -d "$SRC_REPO/.git" ]]; then
-  echo "Source not found: $SRC_REPO" >&2
-  echo "Set WHYNOT_DESIGN_SRC or clone gitea:whynot/whynot-design there." >&2
-  exit 1
-fi
-
-mkdir -p "$VENDOR_DIR/tokens"
-git -C "$SRC_REPO" show "$REF:src/styles/colors_and_type.css" \
-    > "$VENDOR_DIR/colors_and_type.css"
-for f in colors.json type.json spacing.json index.json; do
-  git -C "$SRC_REPO" show "$REF:tokens/$f" > "$VENDOR_DIR/tokens/$f"
-done
-git -C "$SRC_REPO" rev-parse "$REF" > "$REF_FILE"
-
-echo "Vendor synced → $VENDOR_DIR (ref: $(cat "$REF_FILE"))"

static/src/main.css

@@ -1,9 +1,3 @@
-/* whynot-design tokens & semantic element styles (pinned via
-   scripts/sync-whynot-design.sh; see .whynot-design-ref).
-   Must precede the Tailwind import so the @import url(...) for IBM Plex
-   ends up at the top of the generated bundle. */
-@import "./vendor/whynot-design/colors_and_type.css";
-
 @import "tailwindcss";
 
 /* Explicit content sources. Without these, Tailwind's automatic detection
@@ -13,88 +7,44 @@
    template dirs copied in the Dockerfile `assets` stage. */
 @source "../../vergabe_teilnahme/templates";
 
-/* whynot tokens → Tailwind theme. Exposes utilities like bg-paper, text-ink,
-   border-line, bg-paper-2, text-ink-3, … */
 @theme {
-  --color-ink: #0A0A0A;
+  --color-brand-50: #f0f4ff;
-  --color-ink-2: #1F1F1F;
+  --color-brand-100: #dce7ff;
-  --color-ink-3: #5C5C5C;
+  --color-brand-500: #3b5bdb;
-  --color-ink-4: #8A8A8A;
+  --color-brand-600: #2f4ac7;
-  --color-ink-5: #B5B5B3;
+  --color-brand-700: #2541b2;
-  --color-line: #E5E5E2;
+  --color-brand-900: #152d99;
-  --color-line-strong: #C9C9C5;
-  --color-line-soft: #F0F0EC;
-  --color-paper: #FFFFFF;
-  --color-paper-2: #FAFAF7;
-  --color-paper-3: #F4F4EF;
-  --color-hi: #FFE14A;
-  --color-hi-2: #FFD400;
-  --color-hi-ink: #1A1500;
-
-  /* Backwards-compat aliases for legacy `brand-*` utility usage in templates.
-     Keeps Phase 1 a tokens-only swap; templates can migrate to ink/paper at
-     leisure. Map blue-brand scale onto the whynot ink ramp. */
-  --color-brand-50: #FAFAF7;
-  --color-brand-100: #F4F4EF;
-  --color-brand-500: #0A0A0A;
-  --color-brand-600: #1F1F1F;
-  --color-brand-700: #0A0A0A;
-  --color-brand-900: #0A0A0A;
-}
-
-/* Off-spec — vergabe-local until whynot-design defines a canonical
-   destructive color. See history/2026-05-23-whynot-design-cross-framework-analysis.md
-   §4 for context. */
-:root {
-  --danger: #B22222;
-  --danger-fg: #FFFFFF;
 }
 
 @layer base {
+  /* German-app base resets */
   html {
-    font-family: var(--ff-sans, ui-sans-serif), system-ui, sans-serif;
+    font-family: ui-sans-serif, system-ui, sans-serif;
   }
 }
 
 @layer components {
-  /* Cards / sheets — whynot: no shadow, hairline border */
+  .card { @apply bg-white rounded-xl border border-slate-200 shadow-sm p-6; }
-  .card { @apply bg-paper rounded border border-line p-6; }
+  .btn-primary { @apply bg-brand-500 text-white px-4 py-2 rounded-lg hover:bg-brand-600 transition-colors; }
-
+  .btn-secondary { @apply bg-white text-slate-700 border border-slate-300 px-4 py-2 rounded-lg hover:bg-slate-50; }
-  /* Buttons — whynot: 3 variants + off-spec danger */
+  .btn-danger { @apply bg-red-600 text-white px-4 py-2 rounded-lg hover:bg-red-700; }
-  .btn-primary   { @apply bg-ink text-paper px-4 py-2 rounded hover:bg-ink-2 transition-colors; }
+  .btn-ghost { @apply text-slate-600 px-3 py-2 rounded-lg hover:bg-slate-100; }
-  .btn-secondary { @apply bg-paper text-ink border border-line px-4 py-2 rounded hover:bg-paper-2 transition-colors; }
+  .field-row { @apply grid grid-cols-3 gap-4 py-3 border-b border-slate-100 last:border-0; }
-  .btn-ghost     { @apply text-ink-3 px-3 py-2 rounded hover:bg-paper-2; }
+  .field-label { @apply text-sm font-medium text-slate-500 col-span-1; }
-  .btn-danger    { background: var(--danger); color: var(--danger-fg); @apply px-4 py-2 rounded transition-colors; }
+  .field-value { @apply text-sm text-slate-900 col-span-2; }
-  .btn-danger:hover { filter: brightness(0.92); }
+  .phase-badge { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold; }
-
+  .phase-todo { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-slate-200 text-slate-500; }
-  /* Field-row — label/value grid */
+  .phase-active { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-brand-500 text-white; }
-  .field-row   { @apply grid grid-cols-3 gap-4 py-3 border-b border-line-soft last:border-0; }
+  .phase-done { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-green-500 text-white; }
-  .field-label { @apply text-sm font-medium text-ink-3 col-span-1; }
+  .phase-warn { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-amber-400 text-amber-900; }
-  .field-value { @apply text-sm text-ink col-span-2; }
+  .section-title { @apply text-base font-semibold text-slate-900 mb-4; }
-
+  .page-title { @apply text-2xl font-bold text-slate-900; }
-  /* Phase indicators — vergabe semantics (todo/active/done/warn), translated
+  .form-input { @apply w-full rounded-lg border border-slate-300 px-3 py-2 text-sm focus:outline-none focus:ring-2 focus:ring-brand-500 focus:border-transparent; }
-     into whynot palette. `phase-warn` uses --hi (annotation yellow). */
+  .form-label { @apply block text-sm font-medium text-slate-700 mb-1; }
-  .phase-badge  { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold; }
+  .table-base { @apply w-full text-sm text-left; }
-  .phase-todo   { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-paper-3 text-ink-4; }
+  .table-header { @apply bg-slate-50 text-slate-500 font-medium text-xs uppercase tracking-wide; }
-  .phase-active { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-ink text-paper; }
+  .table-row { @apply border-t border-slate-100 hover:bg-slate-50 transition-colors; }
-  .phase-done   { @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold bg-ink-3 text-paper; }
+  .sidebar-link { @apply flex items-center px-3 py-2 rounded-lg text-sm text-slate-700 hover:bg-slate-100 transition-colors; }
-  .phase-warn   { background: var(--hi); color: var(--hi-ink); @apply inline-flex items-center justify-center w-7 h-7 rounded-full text-sm font-bold; }
+  .sidebar-link-active { @apply bg-brand-50 text-brand-700 font-medium; }
-
+  .sidebar-section-btn { @apply w-full flex items-center justify-between px-3 py-2 text-xs font-semibold text-slate-500 uppercase tracking-wide hover:text-slate-700; }
-  /* Titles / sections */
-  .section-title { @apply text-base font-semibold text-ink mb-4; }
-  .page-title    { @apply text-2xl font-medium text-ink tracking-tight; }
-
-  /* Forms */
-  .form-input { @apply w-full rounded border border-line px-3 py-2 text-sm bg-paper focus:outline-none focus:border-ink transition-colors; }
-  .form-label { @apply block text-sm font-medium text-ink-2 mb-1; }
-
-  /* Tables */
-  .table-base   { @apply w-full text-sm text-left; }
-  .table-header { @apply bg-paper-2 text-ink-3 font-medium text-xs uppercase tracking-wide; }
-  .table-row    { @apply border-t border-line-soft hover:bg-paper-2 transition-colors; }
-
-  /* Sidebar */
-  .sidebar-link        { @apply flex items-center px-3 py-2 rounded text-sm text-ink-2 hover:bg-paper-2 transition-colors; }
-  .sidebar-link-active { @apply bg-paper text-ink font-medium; box-shadow: inset 0 0 0 1px var(--line); }
-  .sidebar-section-btn { @apply w-full flex items-center justify-between px-3 py-2 text-xs font-semibold text-ink-4 uppercase tracking-wide hover:text-ink-2; }
 }

static/src/vendor/whynot-design/.whynot-design-ref

@@ -1 +0,0 @@
-9419f166ce395858f55b10a5c72268a1fe9fc9d2

static/src/vendor/whynot-design/colors_and_type.css

@@ -1,273 +0,0 @@
-/* ============================================================
-   WhyNot Design System — Colors & Type
-   ------------------------------------------------------------
-   Neutral, mostly black/white. Color is used SPARINGLY — only
-   one warm accent (annotation yellow) borrowed from the LEGO
-   brick in the logo. The system favours light grey wireframe
-   artefacts over heavy fills.
-   ============================================================ */
-
-/* ---------- Webfonts (Google Fonts, see /fonts for offline) ---------- */
-@import url("https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500;600&family=IBM+Plex+Sans:wght@300;400;500;600;700&family=IBM+Plex+Serif:ital,wght@0,400;0,500;1,400&display=swap");
-
-:root {
-  /* ---------- Base palette: neutrals ---------- */
-  --ink:           #0A0A0A;   /* near-black, the only "fill" most of the time */
-  --ink-2:         #1F1F1F;
-  --ink-3:         #5C5C5C;
-  --ink-4:         #8A8A8A;
-  --ink-5:         #B5B5B3;   /* placeholder text, wireframe labels */
-  --line:          #E5E5E2;   /* default 1px wireframe rule */
-  --line-strong:   #C9C9C5;   /* dividers between sections */
-  --line-soft:     #F0F0EC;   /* hairline within a card */
-  --paper:         #FFFFFF;   /* canvas */
-  --paper-2:       #FAFAF7;   /* sheet, dim canvas */
-  --paper-3:       #F4F4EF;   /* recessed surface, code block bg */
-
-  /* ---------- Foreground / background semantic ---------- */
-  --fg-1:          var(--ink);
-  --fg-2:          var(--ink-3);
-  --fg-3:          var(--ink-4);
-  --fg-mute:       var(--ink-5);
-  --fg-on-dark:    #FAFAF7;
-
-  --bg-1:          var(--paper);
-  --bg-2:          var(--paper-2);
-  --bg-3:          var(--paper-3);
-  --bg-invert:     var(--ink);
-
-  --border:        var(--line);
-  --border-strong: var(--line-strong);
-  --border-soft:   var(--line-soft);
-
-  /* ---------- The single accent: annotation yellow ---------- */
-  /* Lifted from the LEGO brick. Used as highlighter, "draft"
-     stamp, signal-marker. Never as a button fill. */
-  --hi:            #FFE14A;
-  --hi-2:          #FFD400;
-  --hi-ink:        #1A1500;   /* text on yellow */
-
-  /* ---------- Status (for prototype lifecycle, signal strength) ---------- */
-  /* Kept deliberately desaturated so they read as labels, not UI. */
-  --status-raw:        #B5B5B3;   /* S0 — no signal      */
-  --status-weak:       #8A8A8A;   /* S1 — weak signal    */
-  --status-medium:     #5C5C5C;   /* S2 — medium signal  */
-  --status-strong:     #0A0A0A;   /* S3 — strong signal  */
-  --status-commercial: #FFD400;   /* S4 — commercial     */
-
-  /* ---------- Type families ---------- */
-  --ff-sans:    "IBM Plex Sans", ui-sans-serif, system-ui, sans-serif;
-  --ff-mono:    "IBM Plex Mono", ui-monospace, "SF Mono", Menlo, monospace;
-  --ff-serif:   "IBM Plex Serif", "Iowan Old Style", Georgia, serif;
-
-  /* ---------- Type scale (modular, ~1.2) ---------- */
-  --fs-xs:    11px;
-  --fs-sm:    13px;
-  --fs-base:  15px;
-  --fs-md:    17px;
-  --fs-lg:    20px;
-  --fs-xl:    24px;
-  --fs-2xl:   32px;
-  --fs-3xl:   44px;
-  --fs-4xl:   64px;
-  --fs-5xl:   96px;
-
-  --lh-tight:  1.05;
-  --lh-snug:   1.25;
-  --lh-base:   1.5;
-  --lh-loose:  1.7;
-
-  --tr-tight:  -0.02em;
-  --tr-snug:   -0.01em;
-  --tr-base:    0em;
-  --tr-mono:    0.02em;
-  --tr-label:   0.08em;   /* uppercase eyebrow labels */
-
-  /* ---------- Spacing (4px base) ---------- */
-  --sp-1:  4px;
-  --sp-2:  8px;
-  --sp-3:  12px;
-  --sp-4:  16px;
-  --sp-5:  24px;
-  --sp-6:  32px;
-  --sp-7:  48px;
-  --sp-8:  64px;
-  --sp-9:  96px;
-  --sp-10: 128px;
-
-  /* ---------- Radii — small, mostly square ---------- */
-  --r-0:   0px;
-  --r-1:   2px;
-  --r-2:   4px;
-  --r-3:   8px;
-  --r-pill: 999px;
-
-  /* ---------- Elevation — almost none. This is a wireframe system. ---------- */
-  --shadow-0: none;
-  --shadow-1: 0 1px 0 var(--line);
-  --shadow-2: 0 1px 0 var(--line-strong);
-  --shadow-3: 0 4px 12px -6px rgba(10,10,10,0.10);
-}
-
-/* ============================================================
-   Semantic element styles
-   ============================================================ */
-
-html {
-  font-family: var(--ff-sans);
-  font-size: var(--fs-base);
-  line-height: var(--lh-base);
-  color: var(--fg-1);
-  background: var(--bg-1);
-  -webkit-font-smoothing: antialiased;
-  -moz-osx-font-smoothing: grayscale;
-  text-rendering: optimizeLegibility;
-}
-
-body {
-  margin: 0;
-  font-feature-settings: "ss01", "cv11";
-  text-wrap: pretty;
-}
-
-/* ---------- Headings ---------- */
-h1, .h1 {
-  font: 600 var(--fs-3xl)/var(--lh-tight) var(--ff-sans);
-  letter-spacing: var(--tr-tight);
-  margin: 0 0 var(--sp-5);
-  color: var(--fg-1);
-}
-h2, .h2 {
-  font: 500 var(--fs-2xl)/var(--lh-snug) var(--ff-sans);
-  letter-spacing: var(--tr-snug);
-  margin: 0 0 var(--sp-4);
-}
-h3, .h3 {
-  font: 500 var(--fs-xl)/var(--lh-snug) var(--ff-sans);
-  letter-spacing: var(--tr-snug);
-  margin: 0 0 var(--sp-3);
-}
-h4, .h4 {
-  font: 500 var(--fs-lg)/var(--lh-snug) var(--ff-sans);
-  margin: 0 0 var(--sp-2);
-}
-h5, .h5 {
-  font: 500 var(--fs-md)/var(--lh-snug) var(--ff-sans);
-  margin: 0 0 var(--sp-2);
-}
-
-/* ---------- Display (for hero / title slides) ---------- */
-.display-1 {
-  font: 300 var(--fs-5xl)/0.95 var(--ff-sans);
-  letter-spacing: -0.035em;
-  color: var(--fg-1);
-}
-.display-2 {
-  font: 400 var(--fs-4xl)/1.0 var(--ff-sans);
-  letter-spacing: var(--tr-tight);
-}
-
-/* ---------- Body ---------- */
-p {
-  margin: 0 0 var(--sp-4);
-  line-height: var(--lh-base);
-  color: var(--fg-1);
-}
-.lead {
-  font-size: var(--fs-md);
-  line-height: 1.55;
-  color: var(--fg-2);
-}
-small, .small {
-  font-size: var(--fs-sm);
-  color: var(--fg-2);
-}
-
-/* ---------- Eyebrow / uppercase labels (very common in this system) ---------- */
-.eyebrow,
-.label {
-  font: 500 var(--fs-xs)/1.2 var(--ff-mono);
-  letter-spacing: var(--tr-label);
-  text-transform: uppercase;
-  color: var(--fg-3);
-}
-
-/* ---------- Code / mono ---------- */
-code, kbd, samp, pre, .mono {
-  font-family: var(--ff-mono);
-  font-size: 0.92em;
-  letter-spacing: var(--tr-mono);
-}
-code {
-  background: var(--bg-3);
-  padding: 1px 6px;
-  border-radius: var(--r-1);
-  color: var(--ink-2);
-}
-pre {
-  background: var(--bg-3);
-  border: 1px solid var(--border);
-  padding: var(--sp-4);
-  overflow-x: auto;
-  border-radius: var(--r-2);
-  font-size: var(--fs-sm);
-  line-height: var(--lh-snug);
-}
-pre code { background: none; padding: 0; }
-
-/* ---------- Editorial serif moments ---------- */
-.serif       { font-family: var(--ff-serif); }
-.serif-quote {
-  font: 400 italic var(--fs-xl)/1.4 var(--ff-serif);
-  color: var(--fg-2);
-}
-
-/* ---------- Links ---------- */
-a {
-  color: var(--fg-1);
-  text-decoration: underline;
-  text-decoration-color: var(--border-strong);
-  text-underline-offset: 3px;
-  text-decoration-thickness: 1px;
-  transition: text-decoration-color 120ms ease, color 120ms ease;
-}
-a:hover {
-  text-decoration-color: var(--fg-1);
-}
-
-/* ---------- HR ---------- */
-hr {
-  border: 0;
-  border-top: 1px solid var(--border);
-  margin: var(--sp-5) 0;
-}
-
-/* ---------- Highlighter (the one place yellow appears in body copy) ---------- */
-mark, .mark {
-  background: var(--hi);
-  color: var(--hi-ink);
-  padding: 0 2px;
-}
-
-/* ---------- Tables (used in templates) ---------- */
-table {
-  width: 100%;
-  border-collapse: collapse;
-  font-size: var(--fs-sm);
-}
-th, td {
-  text-align: left;
-  padding: var(--sp-3) var(--sp-4);
-  border-bottom: 1px solid var(--border);
-}
-th {
-  font-weight: 500;
-  color: var(--fg-2);
-  font-family: var(--ff-mono);
-  font-size: var(--fs-xs);
-  letter-spacing: var(--tr-label);
-  text-transform: uppercase;
-}
-
-/* ---------- Selection ---------- */
-::selection { background: var(--hi); color: var(--hi-ink); }

static/src/vendor/whynot-design/tokens/colors.json

@@ -1,22 +0,0 @@
-{
-  "$schema": "https://design-tokens.github.io/community-group/format/",
-  "ink":          { "value": "#0A0A0A", "type": "color", "comment": "Near-black. The only fill most of the time." },
-  "ink-2":        { "value": "#1F1F1F", "type": "color" },
-  "ink-3":        { "value": "#5C5C5C", "type": "color" },
-  "ink-4":        { "value": "#8A8A8A", "type": "color" },
-  "ink-5":        { "value": "#B5B5B3", "type": "color", "comment": "Placeholder text, wireframe labels." },
-  "line":         { "value": "#E5E5E2", "type": "color", "comment": "Default 1px wireframe rule." },
-  "line-strong":  { "value": "#C9C9C5", "type": "color" },
-  "line-soft":    { "value": "#F0F0EC", "type": "color" },
-  "paper":        { "value": "#FFFFFF", "type": "color" },
-  "paper-2":      { "value": "#FAFAF7", "type": "color" },
-  "paper-3":      { "value": "#F4F4EF", "type": "color" },
-  "hi":           { "value": "#FFE14A", "type": "color", "comment": "Annotation yellow. Highlighter only, never a button fill." },
-  "hi-2":         { "value": "#FFD400", "type": "color" },
-  "hi-ink":       { "value": "#1A1500", "type": "color", "comment": "Text on yellow." },
-  "status-raw":        { "value": "#B5B5B3", "type": "color", "comment": "S0 — no signal" },
-  "status-weak":       { "value": "#8A8A8A", "type": "color", "comment": "S1 — weak signal" },
-  "status-medium":     { "value": "#5C5C5C", "type": "color", "comment": "S2 — medium signal" },
-  "status-strong":     { "value": "#0A0A0A", "type": "color", "comment": "S3 — strong signal" },
-  "status-commercial": { "value": "#FFD400", "type": "color", "comment": "S4 — commercial" }
-}

static/src/vendor/whynot-design/tokens/index.json

@@ -1,6 +0,0 @@
-{
-  "comment": "Manifest pointing at the three token files. Source-of-truth for any future Style Dictionary build.",
-  "colors":  "./colors.json",
-  "type":    "./type.json",
-  "spacing": "./spacing.json"
-}

static/src/vendor/whynot-design/tokens/spacing.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "https://design-tokens.github.io/community-group/format/",
-  "spacing": {
-    "1":  { "value": "4px",   "type": "dimension" },
-    "2":  { "value": "8px",   "type": "dimension" },
-    "3":  { "value": "12px",  "type": "dimension" },
-    "4":  { "value": "16px",  "type": "dimension" },
-    "5":  { "value": "24px",  "type": "dimension" },
-    "6":  { "value": "32px",  "type": "dimension" },
-    "7":  { "value": "48px",  "type": "dimension" },
-    "8":  { "value": "64px",  "type": "dimension" },
-    "9":  { "value": "96px",  "type": "dimension" },
-    "10": { "value": "128px", "type": "dimension" }
-  },
-  "radius": {
-    "0":    { "value": "0px",   "type": "dimension" },
-    "1":    { "value": "2px",   "type": "dimension" },
-    "2":    { "value": "4px",   "type": "dimension" },
-    "3":    { "value": "8px",   "type": "dimension" },
-    "pill": { "value": "999px", "type": "dimension" }
-  },
-  "shadow": {
-    "0": { "value": "none",                                "type": "shadow" },
-    "1": { "value": "0 1px 0 #E5E5E2",                     "type": "shadow" },
-    "2": { "value": "0 1px 0 #C9C9C5",                     "type": "shadow" },
-    "3": { "value": "0 4px 12px -6px rgba(10,10,10,0.10)", "type": "shadow", "comment": "Floating elements only." }
-  }
-}

static/src/vendor/whynot-design/tokens/type.json

@@ -1,33 +0,0 @@
-{
-  "$schema": "https://design-tokens.github.io/community-group/format/",
-  "family": {
-    "sans":  { "value": "\"IBM Plex Sans\", ui-sans-serif, system-ui, sans-serif", "type": "fontFamily" },
-    "mono":  { "value": "\"IBM Plex Mono\", ui-monospace, \"SF Mono\", Menlo, monospace", "type": "fontFamily" },
-    "serif": { "value": "\"IBM Plex Serif\", \"Iowan Old Style\", Georgia, serif", "type": "fontFamily" }
-  },
-  "size": {
-    "xs":   { "value": "11px", "type": "dimension" },
-    "sm":   { "value": "13px", "type": "dimension" },
-    "base": { "value": "15px", "type": "dimension" },
-    "md":   { "value": "17px", "type": "dimension" },
-    "lg":   { "value": "20px", "type": "dimension" },
-    "xl":   { "value": "24px", "type": "dimension" },
-    "2xl":  { "value": "32px", "type": "dimension" },
-    "3xl":  { "value": "44px", "type": "dimension" },
-    "4xl":  { "value": "64px", "type": "dimension" },
-    "5xl":  { "value": "96px", "type": "dimension" }
-  },
-  "lineHeight": {
-    "tight": { "value": 1.05, "type": "number" },
-    "snug":  { "value": 1.25, "type": "number" },
-    "base":  { "value": 1.5,  "type": "number" },
-    "loose": { "value": 1.7,  "type": "number" }
-  },
-  "tracking": {
-    "tight": { "value": "-0.02em",  "type": "dimension" },
-    "snug":  { "value": "-0.01em",  "type": "dimension" },
-    "base":  { "value": "0em",      "type": "dimension" },
-    "mono":  { "value": "0.02em",   "type": "dimension" },
-    "label": { "value": "0.08em",   "type": "dimension", "comment": "Uppercase eyebrow labels." }
-  }
-}

uv.lock

@@ -362,15 +362,38 @@ wheels = [
 [[package]]
 name = "issue-core"
 version = "0.2.0"
-source = { registry = "https://gitea.coulomb.social/api/packages/coulomb/pypi/simple/" }
+source = { directory = "../issue-core" }
 dependencies = [
     { name = "click" },
     { name = "python-dateutil" },
     { name = "requests" },
 ]
-sdist = { url = "http://gitea.coulomb.social/api/packages/coulomb/pypi/files/issue-core/0.2.0/issue_core-0.2.0.tar.gz", hash = "sha256:cd456ccafdf540f02f7f8b1326e28f8acebcfa0476f3ea2245bd2a5230d85a8d" }
+
-wheels = [
+[package.metadata]
-    { url = "http://gitea.coulomb.social/api/packages/coulomb/pypi/files/issue-core/0.2.0/issue_core-0.2.0-py3-none-any.whl", hash = "sha256:f98b90a13c787095834dbc7ff8b14057718884e01a51c6b13206e438ba1d5f90" },
+requires-dist = [
+    { name = "black", marker = "extra == 'dev'", specifier = ">=22.0" },
+    { name = "click", specifier = ">=8.0.0" },
+    { name = "fastapi", marker = "extra == 'api'", specifier = ">=0.110,<1.0" },
+    { name = "fastapi", marker = "extra == 'dev'", specifier = ">=0.110,<1.0" },
+    { name = "flake8", marker = "extra == 'dev'", specifier = ">=4.0" },
+    { name = "httpx", marker = "extra == 'dev'", specifier = ">=0.27" },
+    { name = "isort", marker = "extra == 'dev'", specifier = ">=5.0" },
+    { name = "jira", marker = "extra == 'jira'", specifier = ">=3.0" },
+    { name = "mypy", marker = "extra == 'dev'", specifier = ">=0.900" },
+    { name = "pre-commit", marker = "extra == 'dev'", specifier = ">=2.0" },
+    { name = "pydantic", marker = "extra == 'api'", specifier = ">=2.0,<3.0" },
+    { name = "pydantic", marker = "extra == 'dev'", specifier = ">=2.0,<3.0" },
+    { name = "pygithub", marker = "extra == 'github'", specifier = ">=1.55" },
+    { name = "pytest", marker = "extra == 'dev'", specifier = ">=6.0" },
+    { name = "pytest-cov", marker = "extra == 'dev'", specifier = ">=2.0" },
+    { name = "pytest-mock", marker = "extra == 'dev'", specifier = ">=3.0" },
+    { name = "python-dateutil", specifier = ">=2.8.0" },
+    { name = "requests", specifier = ">=2.25.0" },
+    { name = "requests", marker = "extra == 'gitea'", specifier = ">=2.25.0" },
+    { name = "sphinx", marker = "extra == 'docs'", specifier = ">=4.0" },
+    { name = "sphinx-click", marker = "extra == 'docs'", specifier = ">=3.0" },
+    { name = "sphinx-rtd-theme", marker = "extra == 'docs'", specifier = ">=1.0" },
+    { name = "uvicorn", extras = ["standard"], marker = "extra == 'api'", specifier = ">=0.27,<1.0" },
 ]
 
 [[package]]
@@ -768,7 +791,7 @@ requires-dist = [
     { name = "django", specifier = ">=5.2" },
     { name = "django-storages", specifier = ">=1.14" },
     { name = "gunicorn", specifier = ">=22.0" },
-    { name = "issue-core", specifier = ">=0.2,<0.3", index = "https://gitea.coulomb.social/api/packages/coulomb/pypi/simple/" },
+    { name = "issue-core", directory = "../issue-core" },
     { name = "psycopg", extras = ["binary"], specifier = ">=3.2" },
     { name = "python-decouple", specifier = ">=3.8" },
     { name = "whitenoise", specifier = ">=6.7" },

vergabe_teilnahme/templates/base.html

@@ -8,7 +8,7 @@
   <link rel="stylesheet" href="{% static 'dist/main.css' %}">
   <script src="{% static 'vendor/alpinejs/alpine.min.js' %}" defer></script>
 </head>
-<body class="bg-paper-2 min-h-screen text-ink">
+<body class="bg-slate-50 min-h-screen">
   {% include "partials/topbar.html" %}
 
   <div class="flex h-[calc(100vh-56px)]">

wiki/DesignSystem.md

@@ -1,50 +0,0 @@
-# Design System
-
-vergabe-teilnahme nutzt das `whynot-design`-System (gitea
-`whynot/whynot-design`) als visuelle Basis.
-
-## Phase 1 — Tokens + CSS (aktiv, ab WP-0017)
-
-- Vendored CSS unter `static/src/vendor/whynot-design/`.
-- Sync via `make sync-whynot-design` (Skript: `scripts/sync-whynot-design.sh`).
-- Gepinnter Commit steht in `static/src/vendor/whynot-design/.whynot-design-ref`.
-- `static/src/main.css` importiert die Vendor-CSS und mappt die whynot-Tokens
-  in den Tailwind-`@theme`-Block: `bg-ink`, `bg-paper`, `text-ink-3`,
-  `border-line` usw. sind als Utility-Klassen verfügbar.
-- Legacy `bg-brand-*` / `text-brand-*` Utilities sind weiterhin nutzbar; sie
-  sind als Aliasse auf die ink/paper-Skala gemappt, damit Page-Templates
-  nicht in einer großen Migration mitgezogen werden müssen.
-
-## Phase 2 — Komponenten (offen)
-
-Adoption der whynot-Komponenten erfolgt sobald upstream Lit Web Components
-und die fehlenden Atome (`Card`, `Modal`, `Input`, `Table`, `Toast`)
-ausliefert. Eigener Workplan wird zu diesem Zeitpunkt angelegt.
-
-## Lokale Abweichungen vom whynot-System
-
-Dokumentiert direkt in `static/src/main.css`:
-
-- **`.btn-danger`** nutzt ein Off-Spec-Rot (`#B22222`, `--danger`-Variable).
-  whynot definiert aktuell keine destruktive Farbe; vergabe-Nutzung erfordert
-  sie für Löschen-Aktionen. Wird zurückgebaut, sobald upstream eine
-  kanonische Lösung definiert.
-
-## Visuelle Hausregeln aus whynot übernommen
-
-- Mostly Black & White; gelber Akzent (`--hi: #FFE14A`) nur als Highlighter /
-  Stamp / S4-Signal — nie als Button-Fill oder Hero-Hintergrund.
-- 1px-Hairlines (`var(--line)` / `border-line`), großzügiger Weißraum,
-  Monospace-Eyebrow-Labels.
-- Keine Schatten auf Cards; nur Popovers bekommen einen weichen 4–12px-Shadow.
-- 0–4px Border-Radius für Cards/Sheets; 8px nur für große Modale; Pill nur
-  für Tag-Capsules.
-- IBM Plex Sans / Mono / Serif via Google-Fonts (`@import url(...)` in der
-  Vendor-CSS). Build-Container und Browser brauchen Internet-Zugriff zu
-  Google Fonts. Air-gapped Deployment würde self-hosting erfordern.
-
-## Hintergrund
-
-- Strategie-Analyse + Komponenten-Lücken-Inventar:
-  `history/2026-05-23-whynot-design-cross-framework-analysis.md`.
-- Adoption-Workplan: `workplans/WP-0017-whynot-design-tokens.md`.

workplans/WP-0001-projektgeruest.md

@@ -4,7 +4,6 @@ title: Projektgerüst — Django-Setup, Tailwind, Dev-Stack
 status: done
 phase: 1-of-12
 created: "2026-05-08"
-domain: communication
 ---
 
 # WP-0001 — Projektgerüst

workplans/WP-0002-fachmodelle.md

@@ -5,7 +5,6 @@ status: done
 phase: 2-of-12
 created: "2026-05-08"
 depends_on: WP-0001
-domain: communication
 ---
 
 # WP-0002 — Fachmodelle

workplans/WP-0003-basis-ui.md

@@ -5,7 +5,6 @@ status: done
 phase: 3-of-12
 created: "2026-05-08"
 depends_on: WP-0002
-domain: communication
 ---
 
 # WP-0003 — Basis-UI

workplans/WP-0004-dashboard-ausschreibungen.md

@@ -5,7 +5,6 @@ status: done
 phase: 4-of-12
 created: "2026-05-08"
 depends_on: WP-0003
-domain: communication
 ---
 
 # WP-0004 — Dashboard und Ausschreibungen-CRUD

workplans/WP-0005-lose-anforderungen.md

@@ -5,7 +5,6 @@ status: done
 phase: 5-of-12
 created: "2026-05-08"
 depends_on: WP-0004
-domain: communication
 ---
 
 # WP-0005 — Lose und Anforderungen

workplans/WP-0006-aufgaben-bieterfragen.md

@@ -5,7 +5,6 @@ status: done
 phase: 6-of-12
 created: "2026-05-08"
 depends_on: WP-0005
-domain: communication
 ---
 
 # WP-0006 — Aufgaben und Bieterfragen

workplans/WP-0007-dokumente.md

@@ -5,7 +5,6 @@ status: done
 phase: 7-of-12
 created: "2026-05-08"
 depends_on: WP-0006
-domain: communication
 ---
 
 # WP-0007 — Dokumentenmanagement

workplans/WP-0008-preise.md

@@ -5,7 +5,6 @@ status: done
 phase: 8-of-12
 created: "2026-05-08"
 depends_on: WP-0007
-domain: communication
 ---
 
 # WP-0008 — Preise und Marktpreisauswertung

workplans/WP-0009-abgabe-nachbetrachtung.md

@@ -5,7 +5,6 @@ status: done
 phase: 9-of-12
 created: "2026-05-08"
 depends_on: WP-0008
-domain: communication
 ---
 
 # WP-0009 — Abgabe (Phase 6/7) und Nachbetrachtung (Phase 8)

workplans/WP-0010-partner-bibliothek.md

@@ -5,7 +5,6 @@ status: done
 phase: 10-of-12
 created: "2026-05-08"
 depends_on: WP-0009
-domain: communication
 ---
 
 # WP-0010 — Subunternehmer, Partner und Bibliothek

workplans/WP-0011-marktbegleiter.md

@@ -5,7 +5,6 @@ status: done
 phase: 11-of-12
 created: "2026-05-08"
 depends_on: WP-0010
-domain: communication
 ---
 
 # WP-0011 — Marktbegleiter-Analyse

workplans/WP-0012-querschnitt.md

@@ -5,7 +5,6 @@ status: done
 phase: 12-of-12
 created: "2026-05-08"
 depends_on: WP-0011
-domain: communication
 ---
 
 # WP-0012 — Querschnitt

workplans/WP-0013-feedback-bugs.md

@@ -5,7 +5,6 @@ status: done
 phase: 13-of-13
 created: "2026-05-14"
 depends_on: WP-0012
-domain: communication
 ---
 
 # WP-0013 — Feedback-Bugs

workplans/WP-0014-aufgaben-lose-scores.md

@@ -5,7 +5,6 @@ status: done
 phase: 14-of-n
 created: "2026-05-14"
 depends_on: WP-0013
-domain: communication
 ---
 
 # WP-0014 — Aufgaben-Phasenzuordnung und Scores

workplans/WP-0015-aufgaben-verknuepfungen-frist-issuefacade.md

@@ -5,7 +5,6 @@ status: done
 phase: 15-of-n
 created: "2026-05-14"
 depends_on: WP-0014
-domain: communication
 ---
 
 # WP-0015 — Aufgaben: Verknüpfungen, implizite Fälligkeit, Issue-Facade

workplans/WP-0016-issue-facade-integration.md

@@ -5,7 +5,6 @@ status: done
 phase: 16-of-n
 created: "2026-05-14"
 depends_on: WP-0015
-domain: communication
 ---
 
 # WP-0016 — Issue-Facade Integration

workplans/WP-0017-whynot-design-tokens.md

@@ -1,11 +1,10 @@
 ---
 id: WP-0017
 title: whynot-design Adoption — Phase 1 (Tokens + CSS)
-status: finished
+status: ready
 phase: 17-of-n
 created: "2026-05-23"
 depends_on: WP-0016
-domain: communication
 ---
 
 # WP-0017 — whynot-design Adoption · Phase 1 (Tokens + CSS)
@@ -42,7 +41,7 @@ Inventar und Lücken-Liste in
 ```task
 id: WP-0017-T01
 title: Vendor-Sync-Skript + initiale Vendor-Übernahme
-status: done
+status: todo
 
 Ziel: deterministisches Pull der whynot-design CSS-/Token-Quellen aus einem
 gepinnten Commit nach `static/src/vendor/whynot-design/`, ohne Docker-Build
@@ -115,7 +114,7 @@ Diffs gegen den Vendor sind Teil des Review-Surfaces beim nächsten Bump.
 ```task
 id: WP-0017-T02
 title: CSS-Integration in static/src/main.css
-status: done
+status: todo
 
 Ziel: whynot-Tokens werden global verfügbar, Tailwind-`@theme`-Mapping
 exponiert sie als Utility-Klassen, vergabe-spezifisches Brand-Blau entfällt.
@@ -229,7 +228,7 @@ später durch self-hosting ersetzt werden — ist heute nicht relevant
 ```task
 id: WP-0017-T03
 title: Base-Template — Body-Hintergrund auf whynot-Palette
-status: done
+status: todo
 
 **`vergabe_teilnahme/templates/base.html`** — Body-Klasse anpassen:
 
@@ -250,7 +249,7 @@ weiterhin parallel zur whynot-Palette.
 ```task
 id: WP-0017-T04
 title: Build + Static-Asset-Prüfung
-status: done
+status: todo
 
 Lokaler Build:
 
@@ -280,7 +279,7 @@ adressieren (visueller Bruch wird dort sichtbar).
 ```task
 id: WP-0017-T05
 title: Big-Bang Smoke-Test — visueller Durchlauf aller Hauptseiten
-status: done
+status: todo
 
 Dev-Server starten und durch die wichtigsten Views klicken. Bei jedem visuellen
 Bruch (Kontrast, weiße Schrift auf weißem Grund, harte Farb-Fremdkörper) eine
@@ -326,7 +325,7 @@ Sichtprüfungs-Beleg.
 ```task
 id: WP-0017-T06
 title: Doku-Update und Phase-2-Pflock
-status: done
+status: todo
 
 **`wiki/`** — neue Datei `wiki/DesignSystem.md` mit knappem Inhalt: