rook-cli 0.2.0__tar.gz → 0.2.1__tar.gz

{rook_cli-0.2.0 → rook_cli-0.2.1}/.claude/worktrees/streamed-orbiting-llama/README.md

@@ -79,21 +79,14 @@ Uninstalling Rook does not delete the database.
 
 **How do I change the archive week layout from Sun–Sat to Mon–Sun?**
 
-There is no in-app setting yet. Update the value directly in the SQLite database.
-Find the exact path with `rook --data-path`, or use the default:
-
 ```powershell
-sqlite3 "$env:LOCALAPPDATA\Rook\data.sqlite3"
-```
-
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'monday');
+rook --week-start monday
 ```
 
 To switch back to Sunday-start:
 
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'sunday');
+```powershell
+rook --week-start sunday
 ```
 
 ## License

rook_cli-0.2.1/.claude/worktrees/streamed-orbiting-llama/src/rook/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.1"

{rook_cli-0.2.0 → rook_cli-0.2.1}/.claude/worktrees/streamed-orbiting-llama/src/rook/__main__.py

@@ -1,5 +1,6 @@
 import sys
 
+from rook import __version__
 from rook.app import RookApp
 from rook.paths import default_database_path
 from rook.persistence.database import connect
@@ -11,9 +12,27 @@ from rook.services.tasks import TaskService
 
 
 def main() -> int:
-    if len(sys.argv) > 1 and sys.argv[1] == "--data-path":
-        print(default_database_path())
-        return 0
+    if len(sys.argv) > 1:
+        if sys.argv[1] == "--version":
+            print(__version__)
+            return 0
+        if sys.argv[1] == "--data-path":
+            print(default_database_path())
+            return 0
+        if sys.argv[1] == "--week-start":
+            value = sys.argv[2].lower() if len(sys.argv) > 2 else ""
+            if value not in ("sunday", "monday"):
+                print("Usage: rook --week-start sunday|monday")
+                return 1
+            db_path = default_database_path()
+            connection = connect(db_path)
+            try:
+                migrate(connection)
+                MetadataRepository(connection).set_week_start_day(0 if value == "monday" else 6)
+            finally:
+                connection.close()
+            print(f"Week start set to {value}.")
+            return 0
 
     db_path = default_database_path()
     connection = connect(db_path)

{rook_cli-0.2.0 → rook_cli-0.2.1}/DEVELOPMENT_GUIDE.md

@@ -1,4 +1,4 @@
-# Rook Product & Engineering RFC
+# Rook Product & Engineering RFC
 ## A Local, Keyboard-First Terminal Daily Journal
 
 > **Accepted brand:** The application is named **Rook**, uses `rook` as its command and Python package slug, and uses `♜` as its default icon. Branding resources remain isolated from domain logic so visual identity can evolve without changing task behavior, persistence, or schema terminology.
@@ -18,11 +18,11 @@
 | Console command | `rook` |
 | Python package slug | `rook` |
 | Status | Draft for implementation |
-| Version | 0.1 |
+| Version | 0.2 |
 | Owner | Project creator and maintainer |
 | Primary implementation environment | Windows with PowerShell and a modern terminal emulator |
 | Intended audience | Project maintainer, contributors, and Claude Code |
-| Implementation status | Not started |
+| Implementation status | Partially implemented — v0.2.0 published to PyPI as `rook-cli` |
 | Last updated | July 2026 |
 
 This document is the authoritative product and engineering specification for version 1 of `Rook`.
@@ -2907,7 +2907,7 @@ The application MUST NOT rely on function keys or terminal-specific scan codes f
 The standard wide footer is:
 
 ```text
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 The footer MUST remain one physical row.
@@ -2917,17 +2917,23 @@ When the terminal is too narrow, the footer must progressively shorten rather th
 Medium-width form:
 
 ```text
-n new  e edit  x done  > migrate  d delete  u undo  r routine  a archive  q quit
+n new  e/Ent edit  x done  > migrate  d delete  u undo  a archive  q quit
 ```
 
 Compact form:
 
 ```text
-n  e  x  >  d  u  r  a  q
+n  e  x  >  d  u  a  q
 ```
 
 A separate Help overlay is not implemented. The footer text is self-explanatory.
 
+Editing footer:
+
+```text
+[Ent] save   [Esc] cancel
+```
+
 ---
 
 # 10. Screen and Component Specifications
@@ -2970,7 +2976,7 @@ rook ♖  Today — Friday, July 24, 2026
   × Submit the expense report
   • B̶u̶y̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶m̶o̶n̶i̶t̶o̶r̶
 
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 Required vertical structure:
@@ -3146,11 +3152,13 @@ The editor MUST NOT open a separate dialog.
 During editing, the shortcut footer SHOULD change to:
 
 ```text
-[Enter] save   [Esc] cancel
+[Ent] save   [Esc] cancel
 ```
 
 This prevents the interface from implying that normal state shortcuts remain active while typing.
 
+After creating a new task, the list scrolls to keep the editing row visible without animation. This is implemented by calling `row.scroll_visible(animate=False)` after `recompose()` in both `begin_create` (when creation starts) and `_save_new_task` (after the task is saved and the list recomposes).
+
 ## 10.8 One-Row Shortcut Footer
 
 The footer is anchored at the bottom of the application viewport.
@@ -3167,13 +3175,13 @@ It MUST:
 Wide Today footer:
 
 ```text
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 Compact Today footer:
 
 ```text
-n  e  x  >  d  u  r  a  ?  q
+n  e  x  >  d  u  a  q
 ```
 
 The footer is instructional, not interactive. Mouse clicking is not required.
@@ -3462,7 +3470,7 @@ rook ♖  Today — Friday, July 24, 2026
   × Submit the expense report
   • B̶u̶y̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶m̶o̶n̶i̶t̶o̶r̶
 
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 ### Today: creating a Task
@@ -3475,7 +3483,7 @@ rook ♖  Today — Friday, July 24, 2026
   × Submit the expense report
 ❯ • Draft blog outline▋
 
-[Enter] save   [Esc] cancel
+[Ent] save   [Esc] cancel
 ```
 
 ### Archive index
@@ -3813,7 +3821,7 @@ The application chooses among three predefined levels based on available width:
 ### Full
 
 ```text
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 ### Condensed
@@ -3825,7 +3833,7 @@ n new  e edit  x done  > migrate  d delete  u undo  r routine  a archive  ? help
 ### Keys only
 
 ```text
-n  e  x  >  d  u  r  a  ?  q
+n  e  x  >  d  u  a  q
 ```
 
 The footer MUST NOT wrap into a second row.
@@ -3911,6 +3919,25 @@ The visual design is acceptable for version 1 when:
 - the mascot and quote do not displace core controls; and
 - the application appears intentional in the primary customized PowerShell environment.
 
+## 11.19 Open Task Visual Treatment — Decision Record
+
+**Decision:** Open tasks render in bold. Tasks in any other state (completed, migrated, deleted) render in normal weight. No color differentiation is applied to task state.
+
+**Iterations tried and rejected:**
+
+1. **Dim (SGR 2) for resolved tasks** — attempted first. On the primary terminal (Windows Terminal with a custom color scheme), `dim` rendered as dark gray/black rather than a dimmer version of the foreground color. SGR 2 does not respect custom terminal palettes and breaks on light-background setups. Rejected.
+2. **CSS opacity on a `-resolved` class** — attempted second. Textual CSS `opacity` works by blending RGB values. The `ansi-dark` theme uses ANSI pass-through colors (terminal-controlled), so Textual has no actual RGB value to blend against. Opacity had no visible effect. Rejected.
+3. **Italic for resolved tasks** — attempted third. User disliked the visual result. Rejected.
+4. **Semi-bold** — user requested after seeing full bold. Impossible: ANSI terminals have only on/off bold (SGR 1); there is no SGR code for semi-bold. Terminal emulators that render bold as a slightly heavier weight are not controllable from the application side. Rejected (impossible).
+
+**Why bold for OPEN works:**
+
+- Bold (SGR 1) is universally supported across terminal emulators and respects any foreground color.
+- Visually: open tasks draw the eye; resolved tasks recede naturally — which matches the intended reading pattern.
+- No color required, fully compatible with the ANSI pass-through approach.
+
+**Implementation:** `row.stylize("bold", len(prefix))` in `render_task_row_text` in `task_row.py`. Only OPEN tasks get bold; all other states render at normal weight. Strikethrough still applied to DELETED tasks.
+
 ---
 
 # 12. Archive Specification
@@ -4545,6 +4572,8 @@ The mascot must not:
 
 Version 1 supports a small finite set of visual mood categories.
 
+**v0.2.0 implementation note:** Mood categories are specified but not implemented in v0.2.0. The current implementation uses a flat pool of mascots and quotes regardless of mood. The mood system is deferred to a future version.
+
 | Category | Trigger concept | Example mascot direction |
 |---|---|---|
 | `fresh` | new day or first ordinary opening | `( ˶ᵔ ᵕ ᵔ˶ )` |
@@ -4633,6 +4662,21 @@ This provides variation across days without visual flicker during ordinary Task
 
 Tests must be able to inject a date and mood input and receive a predictable result.
 
+**v0.2.0 actual implementation:** Date-only deterministic selection. No mood logic. One mascot and one quote per day, seeded by `random.Random(today.toordinal())`.
+
+```python
+import random
+from datetime import date
+
+def pick_for_date(today: date) -> tuple[str, str]:
+    rng = random.Random(today.toordinal())
+    mascot = rng.choice(_MASCOTS)
+    quote = rng.choice(_QUOTES)
+    return mascot, quote
+```
+
+Seeded by 	oday.toordinal() (the day's absolute integer). This gives a stable result for the full day and changes naturally at midnight with the date. No mood input. Tests inject a fixed date for determinism.
+
 ## 14.8 Quote Length
 
 Built-in quotes should generally contain no more than 80 characters including punctuation.
@@ -4759,6 +4803,54 @@ This keeps the initial data model and interface focused.
 
 The architecture should load built-in mascots and quotes from a dedicated resource module so customization can be added later without modifying Task logic.
 
+**v0.2.0 shipped content:**
+
+Both lists are centralized in `src/rook/branding.py`. User-supplied quotes are original or personally meaningful. Mascots are kaomoji/Unicode art combinations with a soft, warm aesthetic.
+
+Mascots (23 kaomoji strings):
+
+```text
+｡・::・ﾟ★ (｡•̀ᴗ-) ✧.。
+˚₊‧꒰ (˶ˆ ᗜ ˆ˵) ꒱‧₊˚
+⋆⁺₊ (｡
+'
+▽
+'
+｡)♡ ₊⁺⋆
+‧₊˚ ☁️ ₊‧₊˚ (˘▽˘)
+∿∿∿ (っ˘ω˘ς) ∿∿∿
+✧˖° (ᵔ◡ᵔ) °˖✧
+˚ ༘ ♡⋆｡˚ (◍•ᴗ•◍)
+‧₊˚ 🖇️✩ ₊˚⊹ (｡•̀ᴗ-)
+⊹ ₊ ⋆ (˘͈ᵕ˘͈ ) ⋆ ₊ ⊹
+˘͈ᵕ˘͈ ₊˚⊹
+(ˊᗜˋ*) ₊˚⊹
+✩₊˚.⋆☾⋆⁺₊✧ (˶˃ ᵕ ˂˶)
+(˶ᵔ ᵕ ᵔ˶) ₊˚⊹
+˚₊‧ ⊹ (˶ˆᗜˆ˵) ⊹ ‧₊˚
+🌸 (◠‿◠✿) 🌸
+⊹˚₊ (ᵒ ᵕ ᵒ) ₊˚⊹
+✦ (。•̀ᴗ-)✦
+₊˚⊹ (ˊ• ॢ•ˋ) ⊹˚₊
+♡₊˚ (˶ᵔ ᵕ ᵔ˶) ˚₊♡
+✿ (◡ ω ◡) ✿
+‧₊˚ ✩ (｡•́‿•̀｡) ✩ ˚₊‧
+⊹ ₊˚ (≧ᴗ≦) ˚₊ ⊹
+❀ (ᵕ—ᴗ—) ❀
+```
+
+Quotes (7):
+
+```text
+You are art. You will never be again.
+Do the thing, and you shall have the power.
+You already survived every day before this one.
+Discipline is a mountain of evidence.
+You are the proof of your own effort.
+Your genius is how everything meets in you.
+Showing up is the whole trick.
+```
+
 ## 14.16 Mascot and Quote Acceptance Criteria
 
 This feature is complete for version 1 when:
@@ -5880,6 +5972,20 @@ The lifecycle is:
 
 The application MUST NOT require a resident background process after the TUI exits.
 
+**v0.2.0 CLI flags:**
+
+The `main()` function in `__main__.py` checks `sys.argv` before launching the TUI. Three utility flags are handled before any database is opened (except `--week-start`, which needs the DB):
+
+| Flag | Behavior |
+|---|---|
+| `--version` | Print `__version__` and exit 0 |
+| `--data-path` | Print the platform-specific SQLite path and exit 0 |
+| `--week-start sunday\|monday` | Update `app_meta.week_start_day` and exit 0 |
+
+Minimal manual `sys.argv` parsing was chosen over `argparse` because the flag set is tiny (three flags, no subcommands) and `argparse` would add boilerplate that obscures simple logic. If flags grow significantly in a future version, migrating to `argparse` or `click` is straightforward.
+
+`--week-start` rationale: previously required users to manually run `sqlite3` and write SQL to change the archive week layout, documented in the README FAQ. The flag removes the need for any SQL knowledge and is consistent with the "feels like a small terminal tool" packaging goal.
+
 ---
 
 ## 16.9 Domain Models
@@ -8076,6 +8182,14 @@ Publishing to PyPI may occur when:
 
 PyPI publication is not required to begin coding or make the repository public.
 
+**v0.2.0 actual state:** Published to PyPI as `rook-cli` (see Section 20.30). Recommended installation:
+
+```powershell
+uv tool install rook-cli
+```
+
+`pip install rook-cli` also works for users who prefer it.
+
 ---
 
 ## 20.10 User Data Directory
@@ -8530,6 +8644,28 @@ Packaging and repository setup are acceptable when:
 - the private RFC is excluded locally if the maintainer chooses not to publish it;
 - and README setup instructions have been followed successfully from a clean environment.
 
+---
+
+## 20.30 Distribution Name, Installation Tool, License, and Build Backend — Decision Record (v0.2.0)
+
+### Distribution name conflict — `rook-cli`
+
+The PyPI distribution name `rook` was already taken by an unrelated package. Chosen resolution: publish as `rook-cli` on PyPI while keeping `rook` as both the console command and the Python import package (`import rook`). Users install with `uv tool install rook-cli` but run `rook` in the terminal. This is a well-established pattern (e.g., `Pillow` installs as `Pillow` but imports as `PIL`). Alternative considered: rename the import package to `rook_cli` — rejected because it would break every import statement and the console command, and the PyPI name is an installation detail users rarely see after the first install.
+
+### Installation tool — uv, not pipx
+
+`pipx` was the original target for end-user installation. On the primary development machine, `pipx` was installed via Scoop but broken (missing `colorama` dependency, not easily fixable). `uv tool install` was used as the alternative. `uv` is now the documented and recommended installation method. `pip install rook-cli` also works for users who prefer it.
+
+### License — Proprietary (not MIT)
+
+Changed from MIT to a custom proprietary license before the first public release. Reason: the maintainer does not want others to redistribute, fork, or build derivative products from the source. The license permits personal, non-commercial use only. In `pyproject.toml`, the non-SPDX identifier `LicenseRef-Proprietary` is used (required because `pyproject.toml`'s `license` field only accepts SPDX identifiers; `LicenseRef-` prefix is the SPDX convention for custom identifiers). The full license text is in `LICENSE`. The plan is to eventually move the project to a personal website and make the GitHub repository private; the public repo is kept open in the interim for visibility and discoverability.
+
+### Build backend — Hatchling
+
+`hatchling` is used as the build backend. Version is read dynamically from `src/rook/__init__.py` via `[tool.hatch.version] path = "src/rook/__init__.py"`. This keeps version defined in one place (importable as `rook.__version__`) and avoids duplication in `pyproject.toml`.
+
+---
+
 # 21. Incremental Development Plan
 
 ## 21.1 Purpose of the Plan
@@ -9006,7 +9142,7 @@ Implement the defining notebook-like interaction: pressing `n` produces a blank
 - `Escape` restores original text during edit.
 - Blank edit cannot save.
 - Printable shortcut letters remain text while editing.
-- Footer changes to `[Enter] save   [Esc] cancel`.
+- Footer changes to `[Ent] save   [Esc] cancel`.
 - Pasted newlines normalize to spaces.
 - Text length is capped at 1,000 code points.
 
@@ -9505,6 +9641,9 @@ feat: add archive weekly view
 
 ## 21.15 Phase 10 — Archive Day Detail
 
+> **Status: Superseded by Phase 9.**
+> The original Phase 9 was a date index screen. The original Phase 10 was a per-day detail drill-down from that index. Both were replaced in the shipped Phase 9 with a single combined weekly view that shows all tasks for the week at once. There is no separate day-detail screen. The design decision is documented in Section 21.14. This section is retained for historical reference.
+
 ### Objective
 
 Allow the user to open a Past Day and read its completed and deleted Tasks as a historical page.
@@ -13368,7 +13507,7 @@ All other keys should be ignored unless the overlay is scrollable.
 Wide Today footer:
 
 ```text
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 Medium Today footer:
@@ -13380,7 +13519,7 @@ n new  e edit  x done  > migrate  d delete  u undo  r routine  a archive  ? help
 Compact Today footer:
 
 ```text
-n  e  x  >  d  u  r  a  ?  q
+n  e  x  >  d  u  a  q
 ```
 
 Footers must shorten rather than wrap. The complete labels remain available in Help.
@@ -13403,7 +13542,7 @@ rook ♖  Today — Friday, July 24, 2026
   × Submit the expense report
   • B̶u̶y̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶m̶o̶n̶i̶t̶o̶r̶
 
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 ## B.2 Empty Today
@@ -13427,7 +13566,7 @@ rook ♖  Today — Friday, July 24, 2026
   × Submit the expense report
 ❯ • Draft blog outline▋
 
-[Enter] save   [Esc] cancel
+[Ent] save   [Esc] cancel
 ```
 
 ## B.4 Editing a Migrated Task
@@ -13440,7 +13579,7 @@ Rook ♜  Friday, July 24, 2026
 ❯ > Call the dentist on Monday▋
   × Submit the expense report
 
-[Enter] save   [Esc] cancel
+[Ent] save   [Esc] cancel
 ```
 
 The edit preserves the Migrated symbol.
@@ -13517,7 +13656,7 @@ Rook ♜  Friday, July 24, 2026
     another full-featured productivity system
   • Reply to Spencer
 
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 Continuation lines align under Task text, not under the selection or state symbols.
@@ -13532,7 +13671,7 @@ Rook ♜  Fri, Jul 24, 2026
   > Call the dentist
   × Submit expenses
 
-n  e  x  >  d  u  r  a  ?  q
+n  e  x  >  d  u  a  q
 ```
 
 The date and footer shorten. The footer does not wrap.
@@ -13546,7 +13685,7 @@ Rook ♜  Fri, Jul 24, 2026
 ❯ • Finish the client deck
   > Call the dentist
 
-n  e  x  >  d  u  r  a  ?  q
+n  e  x  >  d  u  a  q
 ```
 
 The Task region scrolls. The header and footer remain visible when practical.
@@ -13562,7 +13701,7 @@ Rook ♜  Friday, July 24, 2026
 
   Could not save. Your change was not applied.
 
-[n] new   [e] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [r] routine   [a] archive   [?] help   [q] quit
+[n] new   [e/Ent] edit   [x] complete   [>] migrate   [d] delete   [u] undo   [a] archive   [q] quit
 ```
 
 The visible Task state must match the database after the failed write.
@@ -13809,7 +13948,7 @@ Rook ♜  Edit Routine
   □ Brush teeth
 ❯ □ Fill water bottle▋
 
-[Enter] save   [Esc] cancel
+[Ent] save   [Esc] cancel
 ```
 
 ## D.8 Active Routine Session

{rook_cli-0.2.0 → rook_cli-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rook-cli
-Version: 0.2.0
+Version: 0.2.1
 Summary: A local, keyboard-first terminal daily journal.
 Project-URL: Repository, https://github.com/JanviChawla/rook
 Author: Janvi Chawla
@@ -96,21 +96,14 @@ Uninstalling Rook does not delete the database.
 
 **How do I change the archive week layout from Sun–Sat to Mon–Sun?**
 
-There is no in-app setting yet. Update the value directly in the SQLite database.
-Find the exact path with `rook --data-path`, or use the default:
-
 ```powershell
-sqlite3 "$env:LOCALAPPDATA\Rook\data.sqlite3"
-```
-
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'monday');
+rook --week-start monday
 ```
 
 To switch back to Sunday-start:
 
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'sunday');
+```powershell
+rook --week-start sunday
 ```
 
 ## License

{rook_cli-0.2.0 → rook_cli-0.2.1}/README.md

@@ -79,21 +79,14 @@ Uninstalling Rook does not delete the database.
 
 **How do I change the archive week layout from Sun–Sat to Mon–Sun?**
 
-There is no in-app setting yet. Update the value directly in the SQLite database.
-Find the exact path with `rook --data-path`, or use the default:
-
 ```powershell
-sqlite3 "$env:LOCALAPPDATA\Rook\data.sqlite3"
-```
-
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'monday');
+rook --week-start monday
 ```
 
 To switch back to Sunday-start:
 
-```sql
-INSERT OR REPLACE INTO app_meta (key, value) VALUES ('week_start_day', 'sunday');
+```powershell
+rook --week-start sunday
 ```
 
 ## License

rook_cli-0.2.1/src/rook/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.1"

{rook_cli-0.2.0 → rook_cli-0.2.1}/src/rook/__main__.py

@@ -1,5 +1,6 @@
 import sys
 
+from rook import __version__
 from rook.app import RookApp
 from rook.paths import default_database_path
 from rook.persistence.database import connect
@@ -11,9 +12,27 @@ from rook.services.tasks import TaskService
 
 
 def main() -> int:
-    if len(sys.argv) > 1 and sys.argv[1] == "--data-path":
-        print(default_database_path())
-        return 0
+    if len(sys.argv) > 1:
+        if sys.argv[1] == "--version":
+            print(__version__)
+            return 0
+        if sys.argv[1] == "--data-path":
+            print(default_database_path())
+            return 0
+        if sys.argv[1] == "--week-start":
+            value = sys.argv[2].lower() if len(sys.argv) > 2 else ""
+            if value not in ("sunday", "monday"):
+                print("Usage: rook --week-start sunday|monday")
+                return 1
+            db_path = default_database_path()
+            connection = connect(db_path)
+            try:
+                migrate(connection)
+                MetadataRepository(connection).set_week_start_day(0 if value == "monday" else 6)
+            finally:
+                connection.close()
+            print(f"Week start set to {value}.")
+            return 0
 
     db_path = default_database_path()
     connection = connect(db_path)

rook_cli-0.2.0/.claude/worktrees/streamed-orbiting-llama/src/rook/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.0"

rook_cli-0.2.0/src/rook/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.0"