djournal 0.3.0 → 0.3.1
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.
|
@@ -42,7 +42,8 @@ native payloads to these names.
|
|
|
42
42
|
|
|
43
43
|
- Hooks are read-only.
|
|
44
44
|
- `stop_hook_active: true` always permits stopping.
|
|
45
|
-
- `closed` markers must resolve
|
|
46
|
-
|
|
45
|
+
- `closed` markers must resolve to an existing Markdown spine entry under the
|
|
46
|
+
resolved journal root; `.journal/...` paths use `.djournal.json` when a
|
|
47
|
+
global project store is configured.
|
|
47
48
|
- Adapters do not infer task meaning from file changes or unstable transcripts.
|
|
48
49
|
- Adding a harness must not change `AUTOMATION.md` semantics.
|
|
@@ -169,7 +169,7 @@ function handle(payload, options = {}) {
|
|
|
169
169
|
if (match[1].toLowerCase() === "closed" && !validateClosedPath(root, match[2])) {
|
|
170
170
|
return {
|
|
171
171
|
decision: "block",
|
|
172
|
-
reason: "The journal-status closed marker must reference an existing
|
|
172
|
+
reason: "The journal-status closed marker must reference an existing Markdown spine entry under the resolved journal root. In global-store projects, .journal/... paths resolve through .djournal.json.",
|
|
173
173
|
};
|
|
174
174
|
}
|
|
175
175
|
if (match[1].toLowerCase() === "closed") {
|