You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: changes.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,9 @@
2
2
3
3
### unreleased
4
4
5
+
- Expose repo-centric workflow status in `dev.kit`, `dev.kit env`, and `dev.kit repo` output so environment checks, context refresh, and gap repair appear as one repo-owned loop
6
+
- Clarify the repo contract boundary between deterministic structured parsing and interpreted prose/session intent
7
+
5
8
### 0.10.0
6
9
7
10
- Remove `dev.kit agent` so `.rabbit/context.yaml` is the single generated repo contract
Copy file name to clipboardExpand all lines: docs/context-coverage.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ It should answer three questions:
14
14
15
15
For the boundary between generated contract data and durable repo docs, see [Repo Contract Boundary](repo-contract-boundary.md).
16
16
17
+
Structured sources such as YAML, JSON, workflow refs, and manifest metadata should be parsed programmatically where possible. Prose sources such as Markdown docs, prompts, reviews, and session notes should be treated as interpreted intent unless they point to a concrete script, manifest, or command.
Copy file name to clipboardExpand all lines: docs/repo-contract-boundary.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,21 @@ Use **scripts and manifests** for programmatic execution:
20
20
- deploy manifests such as `deploy.yml`
21
21
- checked-in config examples when they are part of the runnable contract
22
22
23
+
Use **structured refs** for deterministic parsing:
24
+
25
+
- YAML and JSON manifests
26
+
- package and tool config files
27
+
- workflow references
28
+
- version, kind, and description metadata
29
+
- explicit command definitions
30
+
31
+
Use **prose and session material** for interpreted intent:
32
+
33
+
- Markdown docs and design notes
34
+
- issue, PR, and review discussions
35
+
- agent prompts and session summaries
36
+
- manual decisions that are not encoded in scripts yet
37
+
23
38
Use **`.rabbit/context.yaml`** for generated operational summary:
24
39
25
40
- direct-read refs
@@ -38,6 +53,8 @@ If a repo needs a compact generated summary for tooling or safe repo-scoped exec
38
53
39
54
If a repo needs something to be executed safely by tools, keep that in a script or manifest rather than only in prose docs.
40
55
56
+
When both structured and prose sources exist, `dev.kit` should parse the structured source first and use prose to explain intent, repair guidance, or open decisions. That keeps automation deterministic while still preserving the human and agent context behind the repo design.
0 commit comments