special-agents 0.8.13 → 0.8.15
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.
|
@@ -36,3 +36,20 @@ Use `/qa-instruction <run> <work> <instruction>` for persisted recipient receipt
|
|
|
36
36
|
`/qa-work <run>` returns pending question IDs and revisions. An explicit `/answer-question <run> <work> <decision> <revision> <choice-or-answer>` targets that exact pending decision. Stale or foreign questions are rejected; the original owner consumes the response and releases its terminal prompt.
|
|
37
37
|
|
|
38
38
|
Ownership repair requires stopped, verified writers. `/qa-repair-plan <run> <work>` provides a read-only source inventory and expected revision. The operator inspects and maps preserved changes, then supplies the exact structured `/qa-repair <JSON>` request. Repair retains original evidence and publishes an immutable audit outcome. Eligible nonterminal work requires fresh QA and invalidates old unconsumed certificates. Completed work stays terminal; waived work remains governed by its existing waiver policy. Report the execution disposition separately from metadata repair. Repair never silently restores files, discards foreign edits, broadens a waiver, or authorizes replay.
|
|
39
|
+
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
after resetting all tickets and restarting the build and doing a hard reset on the branch, i
|
|
43
|
+
|
|
44
|
+
I hit another issue in the same rafi project that had the broken build that we just did tickets for.
|
|
45
|
+
workflow was:
|
|
46
|
+
$ rafi tickets reset --all
|
|
47
|
+
$ rafi build:start-over
|
|
48
|
+
rafi asked which build, i select the current one (the broken one)
|
|
49
|
+
rafi asks how to preserve and restart the run - select archive-restart
|
|
50
|
+
rafi throws error "rafi: unexpected/pre-run changes must be preserved or moved first..."
|
|
51
|
+
$ git reset --hard
|
|
52
|
+
$ rafi start . --steps 8
|
|
53
|
+
rafi error: "rafi: Build <RUN_ID> has unresolved provider dispatch; reconcile before another launch"
|
|
54
|
+
|
|
55
|
+
This last error is the issue. resetting tickets and the build should let me have a clean fresh start. The unresolved provider dispatch is antithical to rafi's function, it feels like a gap that should be handled on any build start over or reset tasks - or maybe there's a better solution, i'm not sure. investigate thoroughly and identify the issue and the best resolution. remember the goal of rafi is to facilitate builds, not stifle them (or rafi itself).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "special-agents",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.15",
|
|
4
4
|
"description": "Rafi library: composable best-practice rules, skills, and agents for Claude Code and Codex.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"type": "module",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"node": ">=20"
|
|
37
37
|
},
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"rafi-spec": "0.8.
|
|
39
|
+
"rafi-spec": "0.8.15",
|
|
40
40
|
"ajv": "^8.20.0",
|
|
41
41
|
"yaml": "^2.5.1"
|
|
42
42
|
},
|