@telora/daemon 0.14.19 → 0.14.21
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 +3 -3
- package/build-info.json +2 -2
- package/dist/cli/connect.d.ts +1 -1
- package/dist/cli/connect.js +1 -1
- package/dist/prompts/starter-prompt.js +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,10 +20,10 @@ Key features:
|
|
|
20
20
|
npm install --save-dev @telora/daemon
|
|
21
21
|
|
|
22
22
|
# Or run directly with npx
|
|
23
|
-
npx @telora/daemon
|
|
23
|
+
npx -p @telora/daemon telora-daemon
|
|
24
24
|
```
|
|
25
25
|
|
|
26
|
-
> **Note:** The `.mcp.json` file for Claude Code integration is auto-generated by `npx telora-daemon init`.
|
|
26
|
+
> **Note:** The `.mcp.json` file for Claude Code integration is auto-generated by `npx -p @telora/daemon telora-daemon init`.
|
|
27
27
|
|
|
28
28
|
## Quick Start
|
|
29
29
|
|
|
@@ -31,7 +31,7 @@ npx @telora/daemon
|
|
|
31
31
|
|
|
32
32
|
```bash
|
|
33
33
|
cd /path/to/your/repo
|
|
34
|
-
npx @telora/daemon init
|
|
34
|
+
npx -p @telora/daemon telora-daemon init
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
The setup wizard will guide you through:
|
package/build-info.json
CHANGED
package/dist/cli/connect.d.ts
CHANGED
|
@@ -112,7 +112,7 @@ export declare function installDaemonIfNeeded(repoPath: string, io: ConnectIO):
|
|
|
112
112
|
*
|
|
113
113
|
* We deliberately do not reuse `startDaemonBackground` from daemon-process.ts
|
|
114
114
|
* because that resolves the entry point relative to *this* file -- which,
|
|
115
|
-
* during a fresh `npx --yes @telora/daemon connect ...` invocation, lives in
|
|
115
|
+
* during a fresh `npx --yes -p @telora/daemon telora-daemon connect ...` invocation, lives in
|
|
116
116
|
* a transient npx cache. Spawning from the local install gives the daemon
|
|
117
117
|
* a stable home for its lifetime.
|
|
118
118
|
*/
|
package/dist/cli/connect.js
CHANGED
|
@@ -195,7 +195,7 @@ export function installDaemonIfNeeded(repoPath, io) {
|
|
|
195
195
|
*
|
|
196
196
|
* We deliberately do not reuse `startDaemonBackground` from daemon-process.ts
|
|
197
197
|
* because that resolves the entry point relative to *this* file -- which,
|
|
198
|
-
* during a fresh `npx --yes @telora/daemon connect ...` invocation, lives in
|
|
198
|
+
* during a fresh `npx --yes -p @telora/daemon telora-daemon connect ...` invocation, lives in
|
|
199
199
|
* a transient npx cache. Spawning from the local install gives the daemon
|
|
200
200
|
* a stable home for its lifetime.
|
|
201
201
|
*/
|
|
@@ -84,8 +84,8 @@ When the user answers:
|
|
|
84
84
|
\`telora_product_delivery_create\`, in priority order. Each
|
|
85
85
|
delivery represents a phase of *one* capability, not a task list.
|
|
86
86
|
Good shapes: foundation/skeleton, primary feature, polish/extension.
|
|
87
|
-
Bad shapes: a single delivery per technical layer (
|
|
88
|
-
|
|
87
|
+
Bad shapes: a single delivery per technical layer ("API",
|
|
88
|
+
"UI", "tests") -- that is a task split, not a phase split.
|
|
89
89
|
3. Do NOT create issues under the deliveries. The team-lead agent
|
|
90
90
|
that runs when the user fires execution will scope tasks. Your
|
|
91
91
|
job is the planning skeleton.
|
|
@@ -106,13 +106,13 @@ the user should do next. The Play button is the next move.
|
|
|
106
106
|
## Constraints (read these before you start)
|
|
107
107
|
|
|
108
108
|
- Stay at the intent layer. If the user's answer is operational
|
|
109
|
-
(
|
|
110
|
-
capability shape (
|
|
111
|
-
type-checking on every commit
|
|
109
|
+
("set up TypeScript with strict mode"), gently re-cast it into a
|
|
110
|
+
capability shape ("a TypeScript project skeleton with strict
|
|
111
|
+
type-checking on every commit") before decomposing.
|
|
112
112
|
- Be brief. This is a script, not a conversation. Phase 1 is one
|
|
113
113
|
line of output. Phase 2 is one question, then a few MCP calls and
|
|
114
114
|
a two-line hand-off. No headings. No bullet lists in the user-
|
|
115
|
-
facing output. No
|
|
115
|
+
facing output. No "As an AI assistant...".
|
|
116
116
|
- Don't propose tasks. Deliveries only. The downstream team agent
|
|
117
117
|
scopes tasks when execution starts.
|
|
118
118
|
- If you can't proceed at any point, surface the specific failure
|