@pmelab/gtd 23.0.0 → 23.2.0

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.
Files changed (5) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/README.md +5 -3
  3. package/dist/gtd.bundle.mjs +844 -1047
  4. package/package.json +1 -1
  5. package/skills/authoring/SKILL.md +7 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pmelab/gtd",
3
- "version": "23.0.0",
3
+ "version": "23.2.0",
4
4
  "private": false,
5
5
  "description": "Git-aware CLI that emits the next prompt for an autonomous coding agent based on the current repository state",
6
6
  "bin": {
package/skills/authoring/SKILL.md CHANGED
@@ -186,9 +186,13 @@ certainly a bug.
186
186
  ## Rules for flow code
187
187
 
188
188
  Flow code is replayed on every command, so it must reach the same steps every
189
- time it sees the same history. `run()` bodies and module top-level code are
190
- exempt. gtd does not read the source ahead of time: breaking a rule shows up
191
- when replay runs, as an error or, for nondeterminism, as a divergence later.
189
+ time it sees the same history. Only `run()` bodies are exempt: module top-level
190
+ code and every local import are evaluated on every command too, so they read no
191
+ `process.env`, clock, network or files either (a per-machine value is an
192
+ `envDefaults` setting). A process records the config's hashes when it starts and
193
+ warns whenever it differs. gtd does not read the source ahead of time: breaking
194
+ a rule shows up when replay runs, as an error or, for nondeterminism, as a
195
+ divergence later.
192
196
 
193
197
  - No IO or nondeterminism in flow code — no clock, randomness, environment,
194
198
  network or filesystem. Read the tree through the helpers; do IO inside a