@connextar/house 0.15.1 → 0.16.0

package/docs/RoutineOperations.md

@@ -14,9 +14,15 @@ This document is the method. An app's `docs/operations/RoutineOperations.md` lin
 2. **Its run log** — one line for every run (§3, step 5), newest first.
 3. **Its standing go-aheads** — any routine the owner has said may read or write production without asking each time, recorded on that routine's row.
 
-Start it from [templates/RoutineOperations.md](templates/RoutineOperations.md): copy it to `docs/operations/RoutineOperations.md`, put the app's name in the title, and fill the register (§5 lists the rows most apps start with). Then add the pointer in §6 to the app's `AGENTS.md`.
+Every app's file has the same three parts, so a reference like "Part 2" means the same thing in each:
 
-The method is not copied into the app. If it needs to change, change it here, so every app changes with it.
+- **Part 1 — The method:** a link here and the four rules an agent needs without leaving the file (read Next due first; never write to production without a yes; how a run is recorded; new routines start Proposed, retired ones are paused), with the status keys.
+- **Part 2 — the register:** 2.1 manual routines, 2.2 automated routines, 2.3 paused.
+- **Part 3 — Run log.**
+
+Start it from [templates/RoutineOperations.md](templates/RoutineOperations.md): copy it to `docs/operations/RoutineOperations.md`, put the app's name in the title, and fill the register (§5 lists the rows most apps start with). The template links the app's own `docs/operations/ReleaseProcess.md`; an app without one links the shared [ReleaseProcess.md](https://github.com/Connextar/cx-house/blob/main/docs/ReleaseProcess.md) instead. Then add the pointer in §6 to the app's `AGENTS.md`.
+
+Part 1 is a summary, not a copy. If the method needs to change, change it here, so every app changes with it, and change the template's Part 1 if one of the four rules moved.
 
 ---
 
@@ -61,9 +67,9 @@ Every routine has one row, with:
 
 ### How the register is laid out
 
-- **Manual routines** — the full table, every field above.
-- **Automated routines** — a shorter table (ID, job, what it does, when, status), headed by a sentence saying where to watch them: the app's job-health page, its operational summary email, its host's cron dashboard. Say how often to look (at least weekly) and when to look sooner.
-- **Paused** — ID, routine, why paused, since.
+- **2.1 Manual routines** — the full table, every field above.
+- **2.2 Automated routines** — a shorter table (ID, job, what it does, when, status), headed by a sentence saying where to watch them: the app's job-health page, its operational summary email, its host's cron dashboard. Say how often to look (at least weekly) and when to look sooner.
+- **2.3 Paused** — ID, routine, why paused, since.
 
 ---
 
@@ -90,7 +96,7 @@ Every routine has one row, with:
 
 ### Retiring a routine
 
-Set it to 🧊 Paused and move it to the Paused table, with the date and the reason. Don't delete it: the run log still points at it, and IDs are never reused.
+Set it to 🧊 Paused and move it to the Paused table (2.3), with the date and the reason. Don't delete it: the run log still points at it, and IDs are never reused.
 
 ### Booking runs
 
@@ -124,17 +130,19 @@ If continuous integration is switched off, add it to the Paused table with the r
 
 ## 6. The pointer in `AGENTS.md`
 
-Add this section to the app's `AGENTS.md`, so every agent reads the register before it starts:
+Add this section to the app's `AGENTS.md`, so every agent reads the register before it starts. Replace the bracketed list with the kinds of check in the app's own register, so an agent knows what it's looking for:
 
 ```markdown
 ## Routine operations
 
-- **`docs/operations/RoutineOperations.md` is the register of recurring checks**,
+- **`docs/operations/RoutineOperations.md` is the register of recurring checks** —
+  [security rounds, pruning, release gates, the browser sweep, bills, privacy] —
   with when each last ran and when it's next due. At the start of a task, read its
   **Next due** column: a routine that is due or overdue runs before new feature
   work, or the owner says why not.
-- After running one, record it as the shared method says
-  (https://github.com/Connextar/cx-house/blob/main/docs/RoutineOperations.md):
-  the full result in its record, a line in the run log, and the row's Last run / Next due / Status.
-  Add a row in the same change set as anything new that needs regular attention.
+- After running one, record it as the shared method says (`@connextar/house`'s
+  [`docs/RoutineOperations.md`](https://github.com/Connextar/cx-house/blob/main/docs/RoutineOperations.md)):
+  the full result in its record, a line in the run log, and the row's Last run /
+  Next due / Status. Add a row in the same change set as anything new that needs
+  regular attention.
 ```

package/docs/templates/RoutineOperations.md

@@ -1,24 +1,43 @@
+<!--
+  Copy to docs/operations/RoutineOperations.md and replace "App name".
+  The ReleaseProcess.md links assume the app has docs/operations/ReleaseProcess.md.
+  If it doesn't, point them at the shared one instead:
+  https://github.com/Connextar/cx-house/blob/main/docs/ReleaseProcess.md
+  Delete this comment once the file is filled in.
+-->
+
 # App name — Routine Operations
 
-> The recurring checks that keep App name ready, aligned and compliant: what each one is for, how often it runs, how to run it, when it last ran and what it found, and when it's next due. The method — the fields, the status keys, how to run, add, retire and book a routine — is the cohort's, in `@connextar/house`: [`docs/RoutineOperations.md`](https://github.com/Connextar/cx-house/blob/main/docs/RoutineOperations.md). This file holds only App name's register and run log. Sits beside [ReleaseProcess.md](ReleaseProcess.md); [`AGENTS.md`](../../AGENTS.md) points here.
+> The recurring checks that keep App name ready, aligned and compliant: what each one is for, how often it runs, how to run it, when it last ran and what it found, and when it's next due. One place to look, so nothing scheduled gets lost in day-to-day work. Sits beside [ReleaseProcess.md](ReleaseProcess.md); [`AGENTS.md`](../../AGENTS.md) points here.
 
 _Last updated: YYYY-MM-DD — first version._
 
-**At the start of a task, read the Next due column.** A 🟨 Due or 🟥 Overdue routine runs before new feature work, or the owner says why not.
+This file follows the cohort's method in `@connextar/house`, [`docs/RoutineOperations.md`](https://github.com/Connextar/cx-house/blob/main/docs/RoutineOperations.md). It holds App name's own register (Part 2) and run log (Part 3).
+
+---
+
+## Part 1 — The method
+
+The method — what a routine is, the register's fields, the status keys, how to run, add, retire and book a routine — is the shared [`docs/RoutineOperations.md`](https://github.com/Connextar/cx-house/blob/main/docs/RoutineOperations.md). Change it there, not here. In short:
+
+- **At the start of a task, read Part 2's Next due column.** A 🟨 Due or 🟥 Overdue routine runs before new feature work, or the owner says why not.
+- **Run it as its How says; never write to production** unless the How says so and the owner has said yes for this run. Reads against production need a go-ahead too, unless the row records a standing one.
+- **Record it:** the full result in its Record, a line in the run log (Part 3), and the row's Last run, Next due and Status. Release if a status document changed ([ReleaseProcess.md](ReleaseProcess.md)).
+- **New routines start ⚪ Proposed**, in the same change set as whatever needs them; retired ones go to 🧊 Paused, never deleted.
 
 Status keys: ✅ On schedule · 🟨 Due · 🟥 Overdue · ⏰ Scheduled · 🤖 Automated · ⚪ Proposed · 🧊 Paused.
 
 ---
 
-## 1. Register
+## Part 2 — App name's register
 
-### 1.1 Manual routines
+### 2.1 Manual routines
 
 | ID     | Routine | Why | When | How | Record | Last run | Next due | Status |
 | ------ | ------- | --- | ---- | --- | ------ | -------- | -------- | ------ |
 | OPS-01 |         |     |      |     |        |          |          |        |
 
-### 1.2 Automated routines
+### 2.2 Automated routines
 
 The app runs these itself. The routine here is **watching** them: say where (a job-health page, a summary email, the host's cron dashboard), how often to look, and when to look sooner.
 
@@ -26,7 +45,7 @@ The app runs these itself. The routine here is **watching** them: say where (a j
 | --- | --- | ------------ | ---- | ------ |
 |     |     |              |      |        |
 
-### 1.3 Paused
+### 2.3 Paused
 
 | ID  | Routine | Why paused | Since |
 | --- | ------- | ---------- | ----- |
@@ -34,7 +53,7 @@ The app runs these itself. The routine here is **watching** them: say where (a j
 
 ---
 
-## 2. Run log
+## Part 3 — Run log
 
 Newest first. One line a run: date · ID · who · result · follow-up.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@connextar/house",
-  "version": "0.15.1",
+  "version": "0.16.0",
   "description": "The pieces every app we build needs and none of them should own a copy of.",
   "license": "MIT",
   "repository": {
@@ -58,6 +58,10 @@
       "types": "./dist/markdown/index.d.ts",
       "default": "./dist/markdown/index.js"
     },
+    "./guides": {
+      "types": "./dist/guides/index.d.ts",
+      "default": "./dist/guides/index.js"
+    },
     "./trail": {
       "types": "./dist/trail/index.d.ts",
       "default": "./dist/trail/index.js"
@@ -198,6 +202,7 @@
     "node": ">=20"
   },
   "dependencies": {
+    "@radix-ui/react-dialog": "^1.3.1",
     "@radix-ui/react-dropdown-menu": "^2.1.24",
     "@radix-ui/react-popover": "^1.1.23",
     "@tiptap/core": "^3.31.3",