@harborppm/cli 0.60.0 → 0.62.0

package/README.md

@@ -28,7 +28,7 @@ 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. `P` runs its pre-mortem: everyone answers "it failed; what happened?" alone for five minutes, then each answer becomes a risk (`r`), folds into one already raised (`m`) or is left out (`l`).
+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`); space picks the card or row you're on, and `m` moves, assigns, dates, pushes a week, sets the priority of or finishes everything picked at once (`u` puts them all back); `e` changes its details: lead, dates, budget, health by hand with a note. `P` runs its pre-mortem: everyone answers "it failed; what happened?" alone for five minutes, then each answer becomes a risk (`r`), folds into one already raised (`m`) or is left out (`l`).
 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.
@@ -177,9 +177,13 @@ harbor raid "TITLE" [--status S] [--owner me|none|NAME] [--impact 1-5] [--probab
 harbor review [WORDS] [--mine|--owner NAME] [--portfolio P] [--done]
                                             the review: programs worst first, with next moves
                                             (reads only; harbor submit moves a task to In review)
+harbor thanks [TASK "LINE"] [--to NAME]     a one-line thanks for a task (--milestone, --decision);
+                                            on its own, the thanks you were given this month
 harbor bridge                               run the review as a meeting: one project a screen,
                                             what changed since the last one, log decisions,
                                             actions and risks live, post the summary to chat
+harbor bridge --list [--program P]          what changed since each program's last review, every
+                                            item, as text (--json for agents); doesn't hold the meeting
 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)
@@ -197,7 +201,7 @@ harbor soundings [PROJECT]
 harbor ashore [--weeks N] [--country CODES|none] [--person NAME]
 harbor limit PROJECT [COLUMN N|none]
 harbor week [--next|--last|--week DATE] [--review]
-harbor week TASK DAY [--hours N] | week TASK --off [DAY] | week --day-hours N
+harbor week TASK --day DAY [--hours N] | week TASK --off [--day DAY] | week --day-hours N
 harbor init [PROJECT] [--hook] [--dry-run]  a project's tasks as files in this repository
 harbor init --local [NAME]                  a plan in this folder alone, no account
 harbor sync [--quiet] [--dry-run]           the files and the website, in step both ways
@@ -207,6 +211,7 @@ harbor fog [--project P]                    tasks nobody has touched for three w
 harbor fog --sweep [--project P]            the same, one at a time: still needed, a new date, or drop it
 harbor fog keep TASK                        it's still needed: out of the fog
 harbor watch [--project P] [--bell]         a live ticker of the harbor's changes
+harbor watch --once [--since TIME] [--json] the latest changes (or all since TIME), once, for scripts
 harbor lifeboats [--program P]              work only one person knows, each with a second pair of hands
 harbor lifeboats N [--person NAME]          adds that second pair of hands
 harbor follow TASK|"RISK" --person NAME     someone follows it too
@@ -218,15 +223,15 @@ harbor agent report TASK "WHAT YOU DID" [--start] [--agent NAME]
 
 `harbor fog` lists the open tasks nobody has opened, moved, edited or commented on for three weeks, longest first. `harbor fog --sweep` walks through them one at a time in a terminal: `k` still needed (clears the fog), `d` a new date, `x` drop it, `s` skip, `q` stop. On the board, in the app and on the website, those cards show dimmed.
 
-`harbor watch` turns a narrow split or a tmux pane into a live ticker of your harbor: cards moving, comments, health changes, a line each as they happen, over the same live updates the website uses. Lines about your own work (your tasks, mentions of you, what you lead) are bright and the rest dim; `--bell` rings the terminal's bell when something of yours changes, and `--project` keeps to one project. `q` stops.
+`harbor watch` turns a narrow split or a tmux pane into a live ticker of your harbor: cards moving, comments, health changes, a line each as they happen, over the same live updates the website uses. Lines about your own work (your tasks, mentions of you, what you lead) are bright and the rest dim; `--bell` rings the terminal's bell when something of yours changes, and `--project` keeps to one project. It starts with the latest few changes and the time it began listening; `--since 14:30` (or a date) starts from then instead. `q` stops; piped or with `--json` (one JSON object a line) it runs until it's killed, and `--once` prints what's there and returns, for scripts.
 
 `harbor lifeboats` lists the work only one person has touched (a project, their corner of one, a task others wait on, their serious risks), numbered, each with someone who has room this week and already works nearby. `harbor lifeboats 2` puts that person on line 2 as a second pair of hands (`--person NAME` for someone else); `harbor follow RR-4 --person Sam` does it for one task. Following doesn't take the work over. `harbor raid "DECISION" --still-stands "WHY"` says a decision that came back for a look still stands.
 
 Agents on the crew: put an AI app on People with Add an agent and assign it tasks like anyone else. An agent working through the CLI (Claude Code, say) runs `harbor agent` for its tasks, in progress first, with their notes, checklists and latest comments. When it's done, `harbor agent report RR-4 "Drafted 12 questions; two need Dana"` adds its note as the agent's comment and moves the task to In review for a person to check. An agent never marks its own work Done.
 
-`harbor week` is your own week, and only you see it: Monday to Friday with the tasks you put on each day, the hours each should take against the hours you work (`--day-hours 8`; 7 unless you say), a warning on a day that's too full, and your open tasks not on a day yet. `harbor week RR-42 wed --hours 3` puts a task on Wednesday (`--next` for next week), `harbor week RR-42 --off` takes it off the week, and from Friday (or with `--review`) it says what you planned against what you finished. The website's Your week is the same plan, with drag and drop.
+`harbor week` is your own week, and only you see it: Monday to Friday with the tasks you put on each day, the hours each should take against the hours you work (`--day-hours 8`; 7 unless you say), a warning on a day that's too full, and your open tasks not on a day yet (ones in review wait on someone else, so they're left out). `harbor week RR-42 --day wed --hours 3` puts a task on Wednesday (`--next` for next week), `harbor week RR-42 --off` takes it off the week, and from Friday (or with `--review`) it says what you planned against what you finished. The website's Your week is the same plan, with drag and drop.
 
-`harbor add --project Trail --comment "From Monday's call" < list.txt` adds one task per line of the file, each with the comment.
+`harbor add --project Trail --comment "From Monday's call" < list.txt` adds one task per line of the file, each with the comment (every option applies to every line); `--dry-run` says what it would add first.
 
 `harbor limit RR` prints how many tasks each of a board's columns takes at once; `harbor limit RR doing 8` changes one (1 to 20, or `none` for no limit), if you own the harbor. `harbor projects --json` carries each board's `limits` too.