Getting started: where to begin on v0.1 (MVP)

## Purpose

This issue exists to answer "where do I start?" without needing any context beyond what's linked here — see `.claude/skills/issue-authoring/SKILL.md` for why that's a hard requirement in this repo.

## Current phase

[Milestone v0.1 (MVP)](https://github.com/kiapanahi/KuriousLabs.WindowsTilingWindowManager/milestone/1) — the first pipeline slice (event ingest through placement) plus enough scaffolding (journal/restore, config loading, CLI, IPC) to make it a real, if minimal, working daemon. See `DESIGN.md` §12 for the full phase breakdown and `README.md` for overall project status.

## Issues with no open dependency — pick any of these first

Every other open issue in v0.1 has an explicit `blocked by` relationship recorded in its sidebar (GitHub's native issue-dependency feature, not just prose) pointing at what needs to land first. These nine currently have none, so they're all valid starting points and can be worked in parallel:

- #1 — Implement the WinEvent ingest pump
- #3 — Implement the Window Registry and manageability filter
- #5 — Implement the Placement Executor
- #7 — Implement the Tier-1 input service (RegisterHotKey)
- #8 — Implement the write-ahead HWND journal and the restore-windows CLI command
- #9 — Implement JSONC config loading with the shipped curated rules file
- #11 — Implement bastionc as a thin named-pipe IPC client
- #13 — Extend Bastion.TestWindows *(good-first-issue)*
- #35 — Replace the flat window list in DwindleLayoutEngine with a persistent SplitTree *(good-first-issue)*

If you're new to the codebase specifically (not just to Bastion's design), #13 or #35 are the narrowest-scoped of the nine.

Everything downstream (#2, #4, #6, #10, #12, #14) declares what it's blocked by directly on the issue — open it and GitHub will show you the exact blocking issue(s), no need to cross-reference this list.

## Keeping this current

This issue should be re-edited (not left stale) whenever: v0.1 closes out and v0.2 becomes the active milestone, or the no-dependency set above changes because something new is filed or an existing blocked-by link is added/resolved.

Read .claude/skills/issue-authoring/SKILL.md, DESIGN.md §12, and README.md, then inspect the v0.1 milestone and each listed issue's dependency state. Keep this issue's no-open-dependency list accurate; it is done when the starting issues and the conditions for re-editing this guide match GitHub's current state.

Written by the indexing model from the issue text.