flagon-io/g1t

public

DEMO.md: fresh work for hello, current names, a fuller pre-recording checklist

- Section 3 asks for work hello does not have yet: --repeat-sep, --sparkle and --lang de, all touching src/lib.rs, src/main.rs and README.md so the overlap radar shows live. - Section 4's brief is --lang it and --lang pt (hello speaks en, es, fr). - Workflows tab, Files changed, "#10 was merged instead", Other attempts at #2, and @g1t as the reviewer. - Before recording: Settings -> Rules -> Require the merge queue; decide Ask a person before merging low-confidence changes (on for hello); mark inbox errors read and check the latest Deploy on flagon-io/g1t is green; warm every page (cold 1.4-2.7 s, warm 0.4-0.9 s).

syntaqxcommitted 1d agoParent70c4d65Browse files

19	19		- Write the three issues for section 3 in a scratch file so they can be
20	20		pasted (titles below). Agents take one to three minutes each: start them,
21	21		talk over sections 4 and 5, and come back.
22		−	- In `flagon-io/hello` Settings → Branches and merging, check **Merge through
23		−	a queue and Merge automatically when ready** are on, so section 7's pull
24		−	requests enter the queue by themselves. (`automation-lab` is set to wait
25		−	for a person, so do not record there.)
	22	+	- In `flagon-io/hello` Settings → Rules, check the ruleset for `main`
	23	+	has Require the merge queue, and in Settings check **Merge
	24	+	automatically when ready** is on, so section 7's pull requests enter the
	25	+	queue by themselves. (`automation-lab` is set to wait for a person, so do
	26	+	not record there.)
	27	+	- In the same settings, **Ask a person before merging low-confidence
	28	+	changes** is on for `hello`. Decide before recording: leave it on and
	29	+	say so if a low-confidence change waits for you in section 7, or turn it
	30	+	off for the take so every green, reviewed pull request lands by itself.
	31	+	Turn it back on afterwards.
26	32		- Write the brief for section 4 in the scratch file too.
	33	+	- Mark the inbox's error notifications read, and check the latest
	34	+	Deploy run on `flagon-io/g1t` is green, since section 9 ends there.
	35	+	- Load every page the script visits once before recording. Cold loads take
	36	+	1.4 to 2.7 seconds; warm ones 0.4 to 0.9.
27	37		- Do not deploy the runner while agents work.
28	38
29	39		## 1. The problem (30 seconds)
⋯
56	66		> `pull_request` and `merge_group` events. Storage is Cloudflare Artifacts;
57	67		> every job runs in its own Cloudflare Container.
58	68
59		−	- Actions tab: the runs, by event. Open one and show the steps and the log.
	69	+	- Workflows tab: the runs, by event. Open one and show the steps and the log.
60	70
61	71		## 3. Many issues, an agent on each (1 minute 30 seconds)
62	72
63	73		Issues tab.
64	74
65	75		- Create three issues quickly, pasting them in:
	76	+	- Add a --repeat-sep flag: `--repeat-sep <s>` prints the greetings
	77	+	`--times` repeats on one line, separated by `<s>`, documented in the
	78	+	README options table.
66	79		- Add a --sparkle flag that ends the greeting with a sparkle emoji.
67		−	- Greet in German with `--lang de`.
68		−	- Explain in the README what happens with no name.
	80	+	- Greet in German with `--lang de` (`Hallo, NAME!`). Today `--lang de`
	81	+	is refused with an error, and a test says so; that test changes too.
	82	+	- All three change `src/lib.rs`, `src/main.rs` and `README.md`, so once
	83	+	the agents have pushed, each pull request shows the others under **Other
	84	+	work is changing the same files**.
69	85		- Tick all three and press Assign to g1t. Say there is nothing
70	86		else to choose: no number of agents, no model. Each issue gets an agent of
71	87		its own and g1t routes the work; every session opens by naming the model
⋯
86	102
87	103		Issues tab, then Outcomes.
88	104
89		−	- Paste a brief, such as: *The greeter should support `--shout`, which
90		−	upper-cases the greeting, documented in the README and covered by tests.*
91		−	Press Plan it. In about twenty seconds an agent has read the
	105	+	- Paste a brief, such as: *The greeter should greet in Italian with
	106	+	`--lang it` (`Ciao, NAME!`) and in Portuguese with `--lang pt`
	107	+	(`Olá, NAME!`). Each language should be documented in the README and
	108	+	covered by tests.* (`hello` speaks `en`, `es` and `fr` today.) Press
	109	+	Plan it. In about twenty seconds an agent has read the
92	110		repository and proposed issues: what each must make true, the files each
93	111		will touch, and which has to land before which.
94	112		- Press Open these and assign g1t. The first issue starts at once. Come
⋯
104	122		Open issue #80, CI: fail when a flag is missing from the README, and its
105	123		pull request #81.
106	124
107		−	- An agent wrote this CI step. Changes tab: the shell step it added to
	125	+	- An agent wrote this CI step. Files changed: the shell step it added to
108	126		`ci.yml`. It went through review and the merge queue like any change.
109	127
110	128		Open issue #84, Add a --reverse flag, and its pull request #85.
⋯
126	144		Open Say goodbye too (#4) and its pull request Add a farewell (#9).
127	145
128	146		- This one was pushed as a branch by a person, the way you already work.
129		−	- Checks failed. Expand `cargo test` and show the output. Changes tab:
130		−	the reviewer's comment sits on the faulty line. The agent's pull request
131		−	for the same issue, #10, passed and was merged; #9 was closed.
	147	+	- Checks failed. A closed pull request keeps its checks: open
	148	+	`cargo test`'s Details and show the log. The agent's pull request for
	149	+	the same issue, #10, passed and was merged; #9 says "#10 was merged
	150	+	instead".
132	151
133		−	Open Greet in Spanish and French (#2).
	152	+	Open Greet in Spanish and French (#2), then either of its pull requests.
134	153
135		−	- Two pull requests for one issue, side by side: checks, size of the change,
136		−	who reviewed. Open one and show Other work is changing the same files.
	154	+	- Other attempts at #2: two agents' pull requests for one issue, side
	155	+	by side, each with its state, its checks, where its review stands and the
	156	+	size of the change. Reviews come from @g1t, the one name all of g1t's own
	157	+	work carries.
	158	+	- Then, on one of section 3's pull requests: **Other work is changing the
	159	+	same files**, naming the other two and the files they share.
137	160
138	161		> This is the overlap radar. g1t says so while the work is still going on,
139	162		> not at the end as a merge conflict. Agents see the same thing through the
140	163		> API, which is how the agents in sections 3 and 4 were told about each other.
141	164
142	165		Open A blank name greets nobody (#1): closed, saying which pull request
143		−	resolved it; the other is marked superseded.
	166	+	resolved it; the other says which one was merged instead.
144	167
145	168		Open Add a --both flag (#88) and its pull request #89, then **Rename
146	169		hail() and part() to greet() and farewell() (#86, pull request #87**).
⋯
165	188
166	189		## 7. The merge queue (1 minute 15 seconds)
167	190
168		−	Back to the pull requests from section 3. Their checks have passed and a g1t
169		−	agent has reviewed them.
	191	+	Back to the pull requests from section 3. Their checks have passed and
	192	+	@g1t has reviewed them.
170	193
171	194		- With auto-merge on, they enter the Merge queue on their own. Open it.
172	195