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
feat(开发线): apply line-family spawn/merge/sync after preflight
When the user asked to spawn, merge, or sync, /dyro-line-family must
run the matching --yes command after preflight. Stay preflight-only
for a dry-run ask. Never invent --push.
dyro --workspace <alias> --dry-run line sync <child>
73
81
```
74
82
75
-
Run only the `--dry-run` that matches the requested verb. If the user supplied `--repos` on `spawn`, repeat that same `--repos` on the dry-run.
76
-
Never pass `--yes` to `line spawn`, `line merge`, or `line sync`.
83
+
Run only the `--dry-run` that matches the requested verb. If the user supplied `--repos` on `spawn`, repeat that same `--repos` on the dry-run and, when applying, on the live command.
77
84
Prefer JSON when the command accepts `--format json`. One JSON document only; `kind=error` is blocked evidence.
78
85
86
+
## Apply
87
+
88
+
When this slash or harness turn is an explicit spawn / merge / sync ask
89
+
and every preflight step passed, run exactly one matching command in
90
+
the same turn:
91
+
92
+
```bash
93
+
dyro --workspace <alias> line spawn <parent><child> --yes
94
+
dyro --workspace <alias> line merge <child> --into <parent> --yes
95
+
dyro --workspace <alias> line sync <child> --yes
96
+
```
97
+
98
+
Print only the matching verb. Repeat user-supplied `--repos` on `spawn` if present.
99
+
Do not add `--push`. Do not run git merge / switch / checkout by hand.
100
+
101
+
Stay preflight-only when the user asked only for preflight or dry-run,
102
+
or when they ran `dyro --dry-run line …` themselves.
103
+
79
104
## Preflight
80
105
81
106
1.`doctor` is observational. Do not treat every `FAIL` as a stop.
@@ -99,13 +124,10 @@ dyro --workspace <alias> doctor
99
124
100
125
or the `--dry-run line spawn|merge|sync` that failed. Do not print a live command.
101
126
102
-
If every preflight step passed, say clearly that `next.commands` did not emit this, then show **one** command for the user to run personally:
127
+
If the user asked only for preflight or dry-run and every preflight step
128
+
passed, say clearly that `next.commands` did not emit this, then show
129
+
**one** command for the user to run personally. Do not run it.
103
130
104
-
```bash
105
-
dyro --workspace <alias> line spawn <parent><child> --yes
106
-
dyro --workspace <alias> line merge <child> --into <parent> --yes
107
-
dyro --workspace <alias> line sync <child> --yes
108
-
```
109
-
110
-
Print only the matching verb. Repeat user-supplied `--repos` on `spawn` if present.
111
-
Do not add `--push`. Do not run that command.
131
+
If the user asked to spawn / merge / sync and every preflight step
132
+
passed, run the matching `--yes` command in this turn, then report what
default_prompt: "Use $dyro-line-family. Preflight with doctor/status/line list and --dry-run line spawn|merge|sync only. Never run --yes, invent --push, or git merge. A printed command is not next.commands."
default_prompt: "Use $dyro-line-family. Preflight with doctor/status/line list and matching --dry-run. If the user asked to spawn|merge|sync and preflight passed, run the matching --yes in this turn. Never invent --push or git merge. Stay preflight-only for a dry-run/preflight ask."
0 commit comments