@harborppm/cli 0.43.0 → 0.44.0

package/README.md

@@ -29,13 +29,13 @@ harbor             # name your harbor and its first project, and you're in
 1. **Today**: today's focus (`f` adds or takes off the task you're on, up to three) and your check-in (`c`); what's on you, late first; who's waiting on you; your risks and issues.
 2. **Inbox**: the same pings as the website: waiting on you, sign-offs, mentions. Enter opens one; it's marked read.
 3. **Projects**: every portfolio, program and project with its health. A project opens on its board (columns side by side; `f` and `p` show only someone's cards or one priority), its list, or its budget and spend ledger (`v`); `e` changes its details: lead, dates, budget, health by hand with a note.
-4. **Programs**: the review: programs worst first, with their lead, end date, late work and where they sit on the priority matrix; `m` writes a next move, `o` and `p` show someone's or one portfolio's. A program shows its projects and milestones side by side (`m` adds a milestone, space ticks one), its next move and health; `v` reads it project by project, each with its bar across the months, open tasks by status and worst risks. A portfolio opens as a board (programs, with risks, next milestones and money beside them); `v` reads it program by program. `e` on a program also names what's holding it back, what it waits on, its impact and its baseline, with its health history below, and `r` reads its status report. A milestone can wait on projects and need someone's sign-off (they approve it or ask for changes). A project's details set its plan by month and what it waits on; a portfolio's set the priority matrix's rules. `:` then "new portfolio" makes one.
-5. **Risks**: the register, worst first; `t`, `o` and `p` narrow it by kind, owner or portfolio, `a` adds closed ones. Enter changes one with every field the website has (status, owner, likelihood, impact, mitigation, contingency, resolution, updates); `n` logs a risk, issue or decision.
+4. **Programs**: the review: programs worst first, with their lead, end date, late work and where they sit on the priority matrix; `m` writes a next move, `h` sets a health by hand (with why) or hands it back to the late work, `o` and `p` show someone's or one portfolio's. A program shows its projects and milestones side by side (`m` adds a milestone, space ticks one), its next move and health; `v` reads it project by project, each with its bar across the months, open tasks by status and worst risks. A portfolio opens as a board (programs, with risks, next milestones and money beside them); `v` reads it program by program. `e` on a program also names what's holding it back, what it waits on, its impact and its baseline, with its health history below, and `r` reads its status report. A milestone can wait on projects and need someone's sign-off (they approve it or ask for changes). A project's details set its plan by month and what it waits on; a portfolio's set the priority matrix's rules. `:` then "new portfolio" makes one.
+5. **Risks**: the register, worst first; `t`, `o` and `p` narrow it by kind, owner or portfolio, `a` adds closed ones, `h` draws the heat map over it and `c` narrows it to one of its cells. Enter changes one with every field the website has (status, owner, likelihood, impact, mitigation, contingency, resolution, rationale, notes, updates); `n` logs a risk, issue or decision.
 6. **People**: open and late work and the next four weeks against each person's capacity; Enter changes their capacity, role, or the time they're promised to a program.
 7. **Roadmap**: a portfolio's programs and projects across the months, in their health's colour, ◆ for milestones.
 8. **History**: who changed what, for a portfolio, program or project (`s` picks which).
 9. **Calendar**: the month with each day's tasks and milestones; arrows move the day, `[` `]` the month, Enter goes into the day's tasks.
-10. **Brief** (`0`): the weekly brief the website writes, for all portfolios or one (`p`).
+10. **Brief** (`0`): the weekly brief the website writes, for all portfolios or one (`p`), with how many programs sit at each health and the notes that opened; `f` swaps in the shipping forecast and `y` copies what's shown (in a terminal that lets apps copy; tmux needs `set-clipboard on`).
 
 A task changes in place too: title, status, owner, due date (`2026-10-14`, `today`, `+3`), priority, project, what it waits on (type a key or words), how it repeats, notes, checklist steps, comments (`C` changes or takes out one of yours).
 
@@ -151,6 +151,14 @@ harbor issue "TITLE" --project P|--program P [--impact 1-5] [--owner NAME]
                     [--due DATE]
 harbor decision "TITLE" --project P|--program P [--owner NAME] [--due DATE]
 harbor risks [words] [--kind risk,issue,decision] [--project P] [--closed]
+harbor raid "TITLE" [--status S] [--owner me|none|NAME] [--impact 1-5] [--probability 1-5]
+                   [--due DATE|none] [--update TEXT] [--mitigation T] [--resolution T] …
+                                            one risk, issue or decision in full, or change it
+harbor review [--mine|--owner NAME] [--portfolio P] [--done]
+                                            the review: programs worst first, with next moves
+harbor next-move PROGRAM "TEXT"             write a program's next move
+harbor health --program P|--project P|--portfolio P STATE [--note WHY]
+                                            set its health by hand (auto hands it back)
 harbor brief [--portfolio P] [--all] [--say] the weekly brief (--all: every late and done task)
 harbor report PROGRAM                       a program's status report, as Markdown
 harbor export tasks PROJECT|risks|review [--all]