@intentius/behold 0.29.48 → 0.29.50

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -97,6 +97,63 @@ an address it answers 404. The kiosk's "Pipeline metrics" pane
97
97
  (web/kiosk-metrics.js) shows only what it returns, and no pane when it
98
98
  returns nothing for the repo.
99
99
 
100
+ ## Runs from chant's run index (behold#815)
101
+
102
+ `behold serve --ci-report-url <url>` (or `BEHOLD_CI_REPORT_URL`) points the
103
+ kiosk's runs pane at chant's run index, `<url>/runs/index.json`
104
+ (ci-run-index/v1, floor `CI_RUN_INDEX_CHANT_FLOOR`, 0.124.31), instead of the
105
+ forge's runs (src/ci-run-index.ts). The text goes through
106
+ `ciRunIndexOf` in src/workspace-reader.ts (contract 1), then the floor against
107
+ the index's own `chant`, then the vendored schema
108
+ (src/ci-run-index-schema/, chant commit in `CI_RUN_INDEX_SCHEMA_SOURCE`) with
109
+ its `status` and `job` enums left out, since v1 adds to them. An entry the
110
+ schema refuses, or whose key is not `<pr>/<commit>[/<member>]`, is dropped and
111
+ listed in `skipped`. `GET /api/chant/ci/runs` answers the runs in demo.runs/v1
112
+ shape; `GET /api/chant/ci/runs/:runId` reads that entry's
113
+ `pr-<job>.events.jsonl` and `pr-<job>.json` under its key only and builds the
114
+ log with `demoRunOf` (src/chant-demo.ts). No events file is one step saying
115
+ so. An apply refused with `plan-changed`, `not-approved` or a wave's
116
+ equivalent exited 3 and is drawn waiting with "the plan moved or waits:
117
+ re-plan and re-approve". So is an apply whose entry has `exitCode: 3` and a
118
+ failure that isn't another refusal (#818; the field follows chant#4165, not
119
+ merged, and isn't in the vendored schema; absent reads as before). `signer` shows only when it is a string; runOrigin's
120
+ URL is the link, named by its host, never by `forge`. The page learns of it
121
+ from `<meta name="kiosk-runs" content="chant-ci">` (web/kiosk-source.js
122
+ `pageRuns`); only the runs pane switches, the cycle and approval panel read
123
+ as before. #818: without the flag, a served workspace's declared
124
+ `ci.reportUrl` (s3:// or file://, read from the `workspace ls` behold already
125
+ makes, `declaredReportUrl` in src/workspace.ts, floor
126
+ `CI_REPORT_URL_CHANT_FLOOR`, 0.124.32, chant#4160) is used, a memberless
127
+ declaration included; the flag overrides it, and each answer's `urlFrom` says
128
+ `flag` or `declaration`. With neither, nothing changes.
129
+
130
+ ## A plan job run locally (behold#685)
131
+
132
+ `POST /api/chant/ci/local` `{job: "plan", commit, pr, env?, base?, member?,
133
+ forge?}` starts `chant ci run plan --local --events-json --env <env> --base
134
+ <sha> --commit <sha> --pr <n> --forge <forge>` (src/ci-local-run.ts, floor
135
+ `CI_RUN_LOCAL_CHANT_FLOOR`, 0.124.32, chant#4161) in the workspace root or the
136
+ named member's declared directory. Each value is checked; the commit and base
137
+ are resolved by `git rev-parse` in the root, the base defaulting to where the
138
+ commit leaves the trunk, the forge to the one workflow directory present. It
139
+ runs through the runner's `track`, so it shares the one-command guard and the
140
+ now-line, and is refused like an Op run: preview `403`, a terragucci or SQL
141
+ Yodeler repo `409` (not allowlisted), `--public` `405` and its GETs `403`.
142
+ stdout lines cross `readRunLine`; stderr is the step output, filed under its
143
+ `[<phase>]`. `GET /api/chant/ci/local/:id` answers the run in demo.run/v1
144
+ (`from: "chant-ci-local"`) and `ci`, CI's run of the same job, commit and
145
+ member from the run index (`ciRunsRoutes`' lookup) when `--ci-report-url` is
146
+ set. The SSE `local-run` event names a run that moved. The page's **Local** tab
147
+ (web/local-run.js) draws both with kiosk-runs.js `renderRun`, and is not drawn
148
+ in a public view, an embed, a static export, preview or a guarded repo.
149
+
150
+ Apply is never started: `job: "apply"` answers `422 local-apply`.
151
+ `--local` does not make an apply safe (it still changes real infrastructure
152
+ and pushes release records and gate facts), and behold has no emulator notion
153
+ that holds for it: `ci run` gives the job a clean environment that keeps HOME,
154
+ so `serve --local`'s emulator env does not reach the job and the operator's
155
+ own credentials would. Cached-step marks wait on chant#4015.
156
+
100
157
  ## A terragucci estate, from its reports (#490)
101
158
 
102
159
  `behold serve <repo> --terragucci <dir|s3://bucket/prefix|https://…>`
@@ -1074,10 +1131,25 @@ superseded, never approvable), `rollback` on an environment's releases, and
1074
1131
  `release` and `rollback` on a deploy record. `releaseColumn: {full, floor}`
1075
1132
  says whether they were read. Below the floor nothing is refused: the column
1076
1133
  comes from `release list` alone with no revoked mark, and the tab says which
1077
- chant would add it. The fixtures in `src/__fixtures__/trunk-lane/` are
1078
- recorded from chant main in the workspace `src/trunk-lane-fixture.ts` makes,
1079
- and `src/trunk-lane-chant.test.ts` reads the same workspace through a real
1080
- chant when `BEHOLD_TEST_CHANT_BIN` names one.
1134
+ chant would add it.
1135
+
1136
+ A mixed environment (#731): from chant 0.124.29
1137
+ (`MIXED_ENVIRONMENT_CHANT_FLOOR`, chant#4035, chant#4072) status gives an
1138
+ environment `mixed` when its components run different releases, or a
1139
+ promote, rollback or redeploy left one `failed` or `gated` (its
1140
+ `outcomes.jsonl` on chant/lifecycle). Each environment carries `mixed[]`, one
1141
+ per member: `components` (each with its recorded `release`, `state` and the
1142
+ `attempt` that left it unsettled), `redeploy` lines and the `rollback` line,
1143
+ as chant wrote them. The tab heads the environment `(mixed)` and shows the
1144
+ lines to copy, run in the member's directory; behold runs none of them.
1145
+ `mixedEnvironments: {read, floor}` says whether it was read; below the floor
1146
+ `mixed` is empty and the lane is drawn as before.
1147
+
1148
+ The fixtures in `src/__fixtures__/trunk-lane/` are recorded from chant main
1149
+ in the workspace `src/trunk-lane-fixture.ts` makes (staging carries a deploy
1150
+ outcome: v3's promote deployed api and failed on web), and
1151
+ `src/trunk-lane-chant.test.ts` reads the same workspace through a real chant
1152
+ when `BEHOLD_TEST_CHANT_BIN` names one.
1081
1153
 
1082
1154
  ## A gate's change set on the graph (#681)
1083
1155
 
@@ -1176,6 +1248,33 @@ the graph draws no marks. A public view refuses the route.
1176
1248
  `BEHOLD_TEST_CHANT_BIN` names one. `status.schema.json` in
1177
1249
  src/trunk-lane-schemas/ is chant main at e9c996e93.
1178
1250
 
1251
+ ## Open decision points beside their gates (#472)
1252
+
1253
+ The approvals inbox is arugula's rail (arugula-salad/arugula#621); behold
1254
+ draws open decision points and answers none. `GET /api/workspace/points`
1255
+ (src/decision-points.ts) reads `chant workspace points --open --json` through
1256
+ the reader's `readPoints` (floor `DECISION_POINTS_CHANT_FLOOR`, 0.107.0, the
1257
+ chant where a gate can ask a point, chant#3170). chant's conformance suite
1258
+ does not list `points`, so the read is not in `BEHOLD_READS`; the reader test
1259
+ holds every other module to not naming it. Each open question carries its
1260
+ point's question, who may answer (the quorum's count and roles), a model's
1261
+ proposal when there is one, and chant's `points answer` line. A gate that
1262
+ asks a point carries `answer` in `workspace status` (the open question's id,
1263
+ its point and path), and its `approve` is that same `points answer` line. The
1264
+ gate strip (web/decision-points.js, web/workspace-gates.js) puts a question
1265
+ on the card of the gate whose `answer.id` names it and gives a question no
1266
+ waiting gate names a card of its own, naming the gate from its
1267
+ `gate:<op>/<gate>@<env>` subject when a gate asked it. Such a gate gets no
1268
+ approve button, framed or not, and `POST /api/workspace/gates/approve`
1269
+ refuses it with `422 decision-point`. Standalone, a point card shows the line
1270
+ as text to copy; framed, it says to answer in the host's rail. There is no
1271
+ write route. Below the floor the route answers the refusal and `degraded`,
1272
+ and the strip says which chant adds points. A public view refuses the route.
1273
+ `src/decision-points-chant.test.ts` reads the workspace
1274
+ `src/decision-points-fixture.ts` makes through a real chant when
1275
+ `BEHOLD_TEST_CHANT_BIN` names one; src/__fixtures__/decision-points/ is
1276
+ chant 0.124.31's output for it.
1277
+
1179
1278
  ## Invariant
1180
1279
 
1181
1280
  If a request would have behold write to a cloud or to source directly, it's wrong.