Files
Orchestrator/.kiro/steering/workspace-notes.md
T

52 lines
2.1 KiB
Markdown

---
inclusion: always
---
# Workspace Notes
## OneDrive File Locks
This workspace is on OneDrive (`OneDrive - Deutsche Bahn`). Files open in the editor or syncing with OneDrive can cause:
- `Move-Item` failures ("Der Prozess kann nicht auf die Datei zugreifen")
- Stale empty directories that can't be deleted
**Workaround:** Use `Copy-Item` + `Remove-Item` instead of `Move-Item`. If removal fails, remove from git tracking (`git rm --cached`) and note the phantom dir. It'll vanish after the user closes their editor.
## PowerShell Command Separator
On this machine, PowerShell is the shell. Use `;` to chain commands, NOT `&&` (which is cmd-only and fails in PowerShell).
## Monorepo Context Assignments
| Context | Repos |
|---------|-------|
| bahn | aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp, Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit, teamlandkarte-mcp, wissensdatenbank (upstream from DB GitLab) |
| dhive | Jury-Voting, Projekt-KIQ-HP |
| privat | CV, NoteGraph (marked for redo) |
| shared | AI-Orchestrator, OrgMyLife, power_skills_and_more, tools/monorepo-cli, references/symphony |
## Key Decisions
- **Bahn repos stay untouched** as independent remotes. The monorepo organizes them but doesn't own them.
- **Jury-Voting** is dhive (not privat). Will be transferred to dhive GitLab later.
- **NoteGraph** needs a complete redo — superseded by the monorepo knowledge store.
- **symphony** is a read-only reference (pinned).
- Secrets go in `.secrets` (gitignored) or encrypted via git-crypt per context.
## Python Environment
The monorepo CLI tool is at `shared/tools/monorepo-cli/`. Tests run with:
```powershell
cd shared\tools\monorepo-cli
python -m pytest tests/ -x --tb=short -q
```
Full property-based tests (Hypothesis) can take 2+ minutes. For quick checks, target specific test files.
## User Preferences
- Andre speaks German, communicates in English, code/docs can be either
- Prefers direct action over asking permission for low-risk changes
- Wants concise plans presented before execution of larger changes
- Uses "go" as confirmation to proceed