@emiliosp/pi-maestro 0.6.2 → 0.6.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.
- package/README.md +6 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,11 +70,14 @@ The owner follows this workflow:
|
|
|
70
70
|
5. Reviews verifier findings and chooses an action for every finding.
|
|
71
71
|
6. Reads Maestro's summary at `candidate-ready` and performs the final review.
|
|
72
72
|
|
|
73
|
-
Maestro starts the verifier after a successful builder run.
|
|
73
|
+
Maestro starts the verifier after a successful builder run.
|
|
74
|
+
Both agents run in the foreground: Pi waits for each run to finish and Maestro shows the current phase in Pi's status, while `pi-subagents` FleetView and `/subagents-fleet` show agent activity and transcripts.
|
|
74
75
|
|
|
75
|
-
The owner must not edit product files while the workflow runs.
|
|
76
|
+
The owner must not edit product files while the workflow runs.
|
|
77
|
+
Maestro can perform temporary experiments with owner agreement during spec preparation and permitted revisions. See [Workflow](docs/workflow.md#spec-approval).
|
|
76
78
|
|
|
77
|
-
|
|
79
|
+
An escalation asks the owner to decide an implementation question, and a finding records a technical issue reported by the verifier. The owner discusses both with Maestro, never directly with the builder or verifier.
|
|
80
|
+
If a contract change is needed during an escalation or finding decision, the owner reviews the revised spec and replies `GREEN FLAG` again. Maestro then starts another builder run.
|
|
78
81
|
|
|
79
82
|
The workflow ends at `candidate-ready`. Rejected findings retain their reasons. Later changes are outside the completed verification. The owner controls any later Git use, pull request, and merge.
|
|
80
83
|
|