# PAISY — Workspace Rules

## Project Context

ADP Germany Java monorepo for payroll/HR government compliance.
Key domains: SV-Meldeverfahren, EAU, EuBP, DaBPV/PUEG, ELStAM, DEÜV, Lohnsteuer.

## Jira

- Project: **ESIDEPAISY**
- All tickets in **German** (summary, description, comments). Technical terms stay as-is.
- Terminal status = `Accepted`
- `customfield_10001` (Feature Link) is mandatory on all tickets — always look up dynamically via JQL, never hardcode
- Sprint ID: always derive from user's most recent ticket (`customfield_10000` with `state=ACTIVE`)
- Branch naming: `current/feature/<module>/TICKET-ID-desc` or `current/bugfix/<module>/TICKET-ID-desc`

### Smart Checklist (Railsware) Formatting

Use `update_checklist` with `items` list. Each item supports:
- `status`: `-` todo, `+` done, `~` in progress, `x` cancelled — append `!` for mandatory (e.g. `-!`)
- `checked: true` → `+`, `checked: false` → `-` (shorthand)
- `name` supports markdown: `**bold**`, `_italic_`, `~~strikethrough~~`, `` `code` ``
- Headers in name: `# H1`, `## H2`, `---` separator (use as standalone items)
- Detail lines: prefix with `> ` in name for sub-text under an item
- Custom statuses: `- [IN QA] Item`, `+ [PASSED] Item`, `-! [IN REVIEW] Item` (mandatory custom)

Default statuses: `TO DO` (-), `IN PROGRESS` (~), `SKIPPED` (x), `DONE` (+)

Example:
```python
[
  {"name": "## Analyse"},
  {"name": "Fehlerursache analysieren", "checked": True},
  {"name": "---"},
  {"name": "## Testing"},
  {"name": "H2-Test", "status": "-!"},  # mandatory todo
  {"name": "Oracle-Test", "status": "~"},  # in progress
  {"name": "QA-Review", "status": "-! [IN QA]"},  # mandatory custom status
]
```

## ADP Docs Wiki

Wiki: `mcp://wikis/adpdocs.de.adp.com` — always check BigMind `adpdocs-index` facts first before fetching.

Key Page IDs (direct access via `get-page`):
- EAU → 25123 | EuBP → 26666 | DaBPV → 27242 | DSBD → 26747 | DSAK → 26748
- DSVV → 18714 | RvBEA → 21174 | EEL → 2724 | ELStAM → 2737 | DEÜV → 5876
- Programmabläufe → 15201 | Einzelaufrufe BATCH → 15250 | Umgebungsvariablen → 22767
- PAISY verwalten → 15180 | Datenbanken verwalten → 15184 | Fehlermeldungen → 15196

## Tech Stack

- Java monorepo, Maven build
- COBOL components (Visual COBOL, formerly NetExpress/ServerExpress)
- Git worktrees for parallel ticket work: `/Users/pplate/git/paisy-<TICKET-ID>`
- Mockito for tests — watch for version conflicts on merge

## Code Conventions

- Code comments and assessment docs: German payroll domain conventions
- Test classes mirror source structure
- Never modify generated sources in `src.gen/`

## PAISY SSH Testing

Use `list-instances` → `set-instance` → `run-program` / `exec-command` for live testing.
Upload JARs with `upload-file` before running programs.

## Git Worktree Visibility

At **every session start** (after `memory_start_session` and `memory_announce_focus`), run:

```bash
git -C /Users/pplate/git/paisy worktree list
git -C /Users/pplate/git/paisy log --all --oneline -15
```

Report to the user:
1. All active worktrees with their branches
2. The last 15 commits across ALL branches (not just the current one)

This ensures visibility into parallel ticket work happening across worktrees, not just the local branch history.