@cratis/pi 7.27.2 → 7.27.3
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.
|
@@ -12,6 +12,7 @@
|
|
|
12
12
|
- 4. Validate authoring and executable readiness
|
|
13
13
|
- 5. Run/render using the same configuration
|
|
14
14
|
- 6. Use Screenplay-owned fixtures
|
|
15
|
+
- Replay the workflow in CI without a Screenplay checkout
|
|
15
16
|
- Edit, render, run and see it in the browser
|
|
16
17
|
- Transcript checklist
|
|
17
18
|
|
|
@@ -170,6 +171,15 @@ Verified public vector and executable checks:
|
|
|
170
171
|
Play proof (test-account decision). UI-profile rejection and render-then-recover
|
|
171
172
|
shipped in Cratis/cli#301.
|
|
172
173
|
|
|
174
|
+
## Replay the workflow in CI without a Screenplay checkout
|
|
175
|
+
|
|
176
|
+
`screens-smoke.sh <work-folder>` in the AI repository's `screens-smoke` verification folder installs the pinned public `cratis` CLI,
|
|
177
|
+
materializes the published `Cratis.Screenplay.CanonicalCorpus` folder source (so the corpus stays Screenplay-owned and
|
|
178
|
+
is never copied), replays the MCP transcript with the revision-checked column edit, renders the edited folder and
|
|
179
|
+
requires the column in the generated `scene.json`. The pins live in `screens-smoke.json` and follow the verified
|
|
180
|
+
vector above; the corpus package is the one that records that vector. The corpus verification job runs it on every
|
|
181
|
+
change. The browser step below needs Docker and Chromium, so it stays a manual step.
|
|
182
|
+
|
|
173
183
|
## Edit, render, run and see it in the browser
|
|
174
184
|
|
|
175
185
|
The loop above proves an agent can change the model. This proves the change
|