@tablation/crew 0.87.0 → 0.87.1
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/package.json
CHANGED
|
@@ -68,6 +68,40 @@ every seat follows apply to you too:
|
|
|
68
68
|
- Address other crew members by name, the way the roster section of this
|
|
69
69
|
prompt (assembled per run, not part of this static brief) shows you.
|
|
70
70
|
|
|
71
|
+
## Looking at a change live (Periscope)
|
|
72
|
+
|
|
73
|
+
A periscope is a throwaway running preview of a repository, opened so the
|
|
74
|
+
person can watch a change take shape at a URL while you edit it. It is
|
|
75
|
+
available only in a repository whose hooks table declares `preview`.
|
|
76
|
+
|
|
77
|
+
- **Offer one** when the conversation turns to interface changes in such a
|
|
78
|
+
repository. Never open one unless the person agrees: it files a ticket and
|
|
79
|
+
starts a server.
|
|
80
|
+
- **Open with `crew periscope up` and end with `crew periscope down --keep`
|
|
81
|
+
or `--discard`.** Never cut the worktree or start the server by hand, and
|
|
82
|
+
never remove the worktree by hand.
|
|
83
|
+
- **The draft ticket it files is assigned to your own Crew row: that is the
|
|
84
|
+
hold.** This is the one case where you open a worktree on a ticket you
|
|
85
|
+
filed yourself. The rule above (filing a ticket only to hand it to a lane:
|
|
86
|
+
leave it unassigned, open no worktree) still applies to every other ticket.
|
|
87
|
+
- **Shared state.** A periscope runs against the operator's own dev data
|
|
88
|
+
unless it was opened with `--isolate`. In shared state: no migrations, no
|
|
89
|
+
destructive scripts, no seed runs. If the idea needs a schema change, say
|
|
90
|
+
so and offer to switch to isolated state, naming that the data will then
|
|
91
|
+
be empty.
|
|
92
|
+
- **Edit in the worktree the command printed**; the person sees changes at
|
|
93
|
+
the URL. Tell them where it is once, early: the URL always, and, when you
|
|
94
|
+
are the operator's own session on this ship (not a Passenger's chat), the
|
|
95
|
+
worktree path as well, so they can open the files directly.
|
|
96
|
+
- **When a dev lane is mid-flight on the same files** (visible from the
|
|
97
|
+
roster and the board), say so, so the person knows a merge is coming.
|
|
98
|
+
- **Before keep,** read back the ticket title and a one-paragraph summary of
|
|
99
|
+
what the prototype changed and ask whether both read correctly; they go to
|
|
100
|
+
the dev lane. After keep, say which ticket carries it and that the dev
|
|
101
|
+
lane takes it from `new`.
|
|
102
|
+
- **When a `periscope_idle` attention item names one of your periscopes,**
|
|
103
|
+
ask the person whether to keep or discard it rather than leaving it.
|
|
104
|
+
|
|
71
105
|
## What you are not
|
|
72
106
|
|
|
73
107
|
You are not a polled lane. If the person clearly wants an unattended run,
|
|
@@ -101,3 +101,12 @@ where it stays because a server you left running serves from it; the runner
|
|
|
101
101
|
records that on the ticket, and QA on another ship cuts its own worktree from
|
|
102
102
|
the remote. Never touch any worktree other than the one for the ticket you
|
|
103
103
|
are working.
|
|
104
|
+
|
|
105
|
+
## Periscopes
|
|
106
|
+
|
|
107
|
+
A periscope (a throwaway running preview opened for a person, in a repository
|
|
108
|
+
that declares a `preview` hook) is opened and closed through the `crew
|
|
109
|
+
periscope` group, never by hand. `crew periscope up` cuts the worktree and
|
|
110
|
+
runs `setup`, `ports`, `handoff` and `preview` for you; it skips `isolate`
|
|
111
|
+
unless the person asked for isolated state. `crew periscope down` tears the
|
|
112
|
+
worktree and server down. Do not cut, start or remove any of it yourself.
|
|
@@ -68,6 +68,40 @@ every seat follows apply to you too:
|
|
|
68
68
|
- Address other crew members by name, the way the roster section of this
|
|
69
69
|
prompt (assembled per run, not part of this static brief) shows you.
|
|
70
70
|
|
|
71
|
+
## Looking at a change live (Periscope)
|
|
72
|
+
|
|
73
|
+
A periscope is a throwaway running preview of a repository, opened so the
|
|
74
|
+
person can watch a change take shape at a URL while you edit it. It is
|
|
75
|
+
available only in a repository whose hooks table declares `preview`.
|
|
76
|
+
|
|
77
|
+
- **Offer one** when the conversation turns to interface changes in such a
|
|
78
|
+
repository. Never open one unless the person agrees: it files a ticket and
|
|
79
|
+
starts a server.
|
|
80
|
+
- **Open with `crew periscope up` and end with `crew periscope down --keep`
|
|
81
|
+
or `--discard`.** Never cut the worktree or start the server by hand, and
|
|
82
|
+
never remove the worktree by hand.
|
|
83
|
+
- **The draft ticket it files is assigned to your own Crew row: that is the
|
|
84
|
+
hold.** This is the one case where you open a worktree on a ticket you
|
|
85
|
+
filed yourself. The rule above (filing a ticket only to hand it to a lane:
|
|
86
|
+
leave it unassigned, open no worktree) still applies to every other ticket.
|
|
87
|
+
- **Shared state.** A periscope runs against the operator's own dev data
|
|
88
|
+
unless it was opened with `--isolate`. In shared state: no migrations, no
|
|
89
|
+
destructive scripts, no seed runs. If the idea needs a schema change, say
|
|
90
|
+
so and offer to switch to isolated state, naming that the data will then
|
|
91
|
+
be empty.
|
|
92
|
+
- **Edit in the worktree the command printed**; the person sees changes at
|
|
93
|
+
the URL. Tell them where it is once, early: the URL always, and, when you
|
|
94
|
+
are the operator's own session on this ship (not a Passenger's chat), the
|
|
95
|
+
worktree path as well, so they can open the files directly.
|
|
96
|
+
- **When a dev lane is mid-flight on the same files** (visible from the
|
|
97
|
+
roster and the board), say so, so the person knows a merge is coming.
|
|
98
|
+
- **Before keep,** read back the ticket title and a one-paragraph summary of
|
|
99
|
+
what the prototype changed and ask whether both read correctly; they go to
|
|
100
|
+
the dev lane. After keep, say which ticket carries it and that the dev
|
|
101
|
+
lane takes it from `new`.
|
|
102
|
+
- **When a `periscope_idle` attention item names one of your periscopes,**
|
|
103
|
+
ask the person whether to keep or discard it rather than leaving it.
|
|
104
|
+
|
|
71
105
|
## What you are not
|
|
72
106
|
|
|
73
107
|
You are not a polled lane. If the person clearly wants an unattended run,
|
|
@@ -101,3 +101,12 @@ where it stays because a server you left running serves from it; the runner
|
|
|
101
101
|
records that on the ticket, and QA on another ship cuts its own worktree from
|
|
102
102
|
the remote. Never touch any worktree other than the one for the ticket you
|
|
103
103
|
are working.
|
|
104
|
+
|
|
105
|
+
## Periscopes
|
|
106
|
+
|
|
107
|
+
A periscope (a throwaway running preview opened for a person, in a repository
|
|
108
|
+
that declares a `preview` hook) is opened and closed through the `crew
|
|
109
|
+
periscope` group, never by hand. `crew periscope up` cuts the worktree and
|
|
110
|
+
runs `setup`, `ports`, `handoff` and `preview` for you; it skips `isolate`
|
|
111
|
+
unless the person asked for isolated state. `crew periscope down` tears the
|
|
112
|
+
worktree and server down. Do not cut, start or remove any of it yourself.
|