feat(lead): lead-radar ich an Cockpit-Datenschicht angepasst, Pfade ap/PM

- ich.md: Input-Keys des neuen Scope ich, Sally über attendanceStatus und tasks-Sections, Abwesenheitsregel nur bei Terminkollision, Häufungs-Check je Tag, Eingang IT, Persist-Schritt mit State-Lauf und OKF-Pflege
- execute.md: Umzug in anderes Projekt, --todoset, Mitgliedschaftsprüfung
- SKILL.md: Personen-ID-Tabelle als Quelle, Laufzeit, Drift-Pflicht für neue IDs
- person.md: „Nicht delegierbar“, Stub-Hinweis
- alle lead-*-Skills: veraltete Pfade p/PM → ap/PM

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
m3ta-chironandClaude Fable 5.1 committed 2026-11-10 09:41:12 +01:00
1 parent 16dac49044
commit 06acee80c2
11 files changed
+75 -60

No files matched your search

+8 -8
View File
@@ -23,10 +23,10 @@ Invocation: `/lead-radar <tag|freitag|ich|person <slug>|portfolio>`. Without a m
Read before acting; these hold the facts, this skill holds only behaviour:
- `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md`: task rules, the six 👥 IT lists, 30-day rule, Zammad boundary, **approval protocol** (binding for every write)
- `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`: project, list and folder IDs
- `/home/sascha.koenig/p/PM/.okf/organization/*.md`: people (role, skills, Basecamp person ID, Zammad login)
- `/home/sascha.koenig/p/PM/tools/it-cockpit/README.md`: the data layer and what each scope returns
- `/home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md`: task rules, the six 👥 IT lists, 30-day rule, Zammad boundary, **approval protocol** (binding for every write)
- `/home/sascha.koenig/ap/PM/.okf/systems/basecamp.md`: project, list and folder IDs
- `/home/sascha.koenig/ap/PM/.okf/organization/*.md`: people (role, skills, Basecamp person ID, Zammad login)
- `/home/sascha.koenig/ap/PM/tools/it-cockpit/README.md`: the data layer and what each scope returns
An ID that fails: resolve it by name, carry on, and add the mismatch to the Drift block.
@@ -44,20 +44,20 @@ Show the comment in the proposal exactly as it will be posted, marker included.
**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`.
- Basecamp: `[@Vorname Nachname](person:<person-id>)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal.
- Basecamp: `[@Vorname Nachname](person:<person-id>)`, ID from `.okf/organization/` or, for colleagues outside the IT team, from the table "Basecamp-Personen-IDs häufiger Gegenüber" in `.okf/systems/basecamp.md`; fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. A person found only via the fallback becomes a Drift proposal (add the row to that table). Milan Urban's Basecamp display name is `milan`; mention him with his full name anyway. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal.
- Zammad (internal note, `text/html`): `<a href="<zammad-url>/#user/profile/<uid>" data-mention-user-id="<uid>">Vorname Nachname</a>`, uid via `GET /api/v1/users/search?query=<login>`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group.
## Steps
### 1. Pull the data
From `/home/sascha.koenig/p/PM`:
From `/home/sascha.koenig/ap/PM`:
```bash
python3 tools/it-cockpit/cockpit.py --json --scope <mode> [--person <slug>]
```
For `ich` add `--dry-run`: the state is written only at the very end of the run, after execution (see `references/ich.md`). A run takes 20–90 s. Save the JSON to the scratchpad and work from that file. Every output carries `drift` and `errors`; an entry under `errors` (e.g. Zammad without `ZAMMAD_TOKEN`) means that source is blind for this run: say so in one line at the top of the Lagebild and continue with the rest. Use live `basecamp` calls only for detail questions the cockpit does not answer (comments under an item, a card's history).
For `ich` add `--dry-run`: the state is written only at the very end of the run, after execution (see `references/ich.md`). A cockpit run takes 20–90 s; a full `ich` run with Sally and execution takes 30–60 minutes of tool time, say so when the user asks for a quick look. Save the JSON to the scratchpad and work from that file. Every output carries `drift` and `errors`; an entry under `errors` (e.g. Zammad without `ZAMMAD_TOKEN`) means that source is blind for this run: say so in one line at the top of the Lagebild and continue with the rest. Use live `basecamp` calls only for detail questions the cockpit does not answer (comments under an item, a card's history).
**Done when** the JSON is on disk and you know which sources are blind.
@@ -95,7 +95,7 @@ Follow [references/execute.md](references/execute.md): one command per change, t
### 5. Persist and report
For `ich` and `portfolio` write the document as the mode's reference describes, reflecting what was actually executed. Other modes write nothing.
For `ich` and `portfolio` write the document as the mode's reference describes, reflecting what was actually executed, then write the mode's state (`ich`: second cockpit run without `--dry-run`). Other modes write nothing. Anything the run created that the OKF must know (folder IDs, person IDs, list IDs) is proposed under ⚠️ Drift in step 3 and written in step 4; a run never leaves an ID only in a Basecamp document.
Report in German: executed items with links, failed items with error, document URL (if any), open `Für dich:` points.