instar 0.3.3 → 0.3.4
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/dist/commands/init.js +23 -0
- package/dist/commands/setup.js +22 -0
- package/dist/scaffold/templates.js +23 -0
- package/package.json +1 -1
package/dist/commands/init.js
CHANGED
|
@@ -399,8 +399,28 @@ Your identity is not fixed at creation. It grows through experience. As you work
|
|
|
399
399
|
- Server: \`instar server start\` (port ${port})
|
|
400
400
|
- Status: \`curl http://localhost:${port}/health\`
|
|
401
401
|
|
|
402
|
+
### Reporting Issues & Feedback (IMPORTANT — Read This First)
|
|
403
|
+
|
|
404
|
+
**You have a built-in feedback system. NEVER use GitHub, \`gh\`, or any external issue tracker.**
|
|
405
|
+
|
|
406
|
+
When something isn't working with instar, or the user wants a feature, use your feedback API:
|
|
407
|
+
|
|
408
|
+
\`\`\`bash
|
|
409
|
+
curl -X POST http://localhost:${port}/feedback \\
|
|
410
|
+
-H 'Content-Type: application/json' \\
|
|
411
|
+
-d '{"type":"bug","title":"Short description","description":"Full details with context"}'
|
|
412
|
+
\`\`\`
|
|
413
|
+
|
|
414
|
+
This routes feedback to the Instar maintainers automatically. Valid types: \`bug\`, \`feature\`, \`improvement\`, \`question\`.
|
|
415
|
+
|
|
416
|
+
**NEVER use \`gh issue\`, \`gh api\`, or GitHub CLI to file issues.** The feedback API is your channel.
|
|
417
|
+
- View submitted feedback: \`curl http://localhost:${port}/feedback\`
|
|
418
|
+
- Retry failed forwards: \`curl -X POST http://localhost:${port}/feedback/retry\`
|
|
419
|
+
|
|
402
420
|
### What You Have (Capabilities)
|
|
403
421
|
|
|
422
|
+
**Feedback System** — Report bugs, request features, suggest improvements. All via \`POST /feedback\`. NOT GitHub.
|
|
423
|
+
|
|
404
424
|
**Job Scheduler** — You can run tasks on a schedule. Jobs are defined in \`.instar/jobs.json\`.
|
|
405
425
|
- View jobs: \`curl http://localhost:${port}/jobs\`
|
|
406
426
|
- Trigger a job: \`curl -X POST http://localhost:${port}/jobs/SLUG/trigger\`
|
|
@@ -442,6 +462,8 @@ When a user asks for something you can't do yet, **build it**:
|
|
|
442
462
|
|
|
443
463
|
### Anti-Patterns to Override
|
|
444
464
|
|
|
465
|
+
**"Use GitHub for Issues"** — NEVER use \`gh issue\`, \`gh api\`, or GitHub to report bugs or request features. You have a built-in feedback API (\`POST /feedback\`) that handles this automatically. GitHub is not your channel — the feedback system is.
|
|
466
|
+
|
|
445
467
|
**"Escalate to Human"** — You encounter something unfamiliar and flag it as "needs user action." 5 minutes of research almost always reveals a solution. "I don't know how" is a research prompt, not a stopping point.
|
|
446
468
|
|
|
447
469
|
**"Ask Permission"** — You finish 90% of a task and ask "Want me to [obvious next step]?" If the user said "do X" and the next step is obvious, do it. Only pause for destructive, irreversible, or genuinely ambiguous actions.
|
|
@@ -716,6 +738,7 @@ if [ -d "$INSTAR_DIR/relationships" ]; then
|
|
|
716
738
|
CONTEXT="\${CONTEXT}You have \${REL_COUNT} tracked relationships in .instar/relationships/.\\n"
|
|
717
739
|
fi
|
|
718
740
|
fi
|
|
741
|
+
CONTEXT="\${CONTEXT}IMPORTANT: To report bugs or request features, use POST /feedback on your local server. NEVER use gh or GitHub directly.\\n"
|
|
719
742
|
[ -n "$CONTEXT" ] && echo "$CONTEXT"
|
|
720
743
|
`, { mode: 0o755 });
|
|
721
744
|
// Dangerous command guard
|
package/dist/commands/setup.js
CHANGED
|
@@ -765,8 +765,28 @@ Your identity is not fixed at creation. It grows through experience. As you work
|
|
|
765
765
|
- Server: \`instar server start\` (port ${port})
|
|
766
766
|
- Status: \`curl http://localhost:${port}/health\`
|
|
767
767
|
|
|
768
|
+
### Reporting Issues & Feedback (IMPORTANT — Read This First)
|
|
769
|
+
|
|
770
|
+
**You have a built-in feedback system. NEVER use GitHub, \`gh\`, or any external issue tracker.**
|
|
771
|
+
|
|
772
|
+
When something isn't working with instar, or the user wants a feature, use your feedback API:
|
|
773
|
+
|
|
774
|
+
\`\`\`bash
|
|
775
|
+
curl -X POST http://localhost:${port}/feedback \\
|
|
776
|
+
-H 'Content-Type: application/json' \\
|
|
777
|
+
-d '{"type":"bug","title":"Short description","description":"Full details with context"}'
|
|
778
|
+
\`\`\`
|
|
779
|
+
|
|
780
|
+
This routes feedback to the Instar maintainers automatically. Valid types: \`bug\`, \`feature\`, \`improvement\`, \`question\`.
|
|
781
|
+
|
|
782
|
+
**NEVER use \`gh issue\`, \`gh api\`, or GitHub CLI to file issues.** The feedback API is your channel.
|
|
783
|
+
- View submitted feedback: \`curl http://localhost:${port}/feedback\`
|
|
784
|
+
- Retry failed forwards: \`curl -X POST http://localhost:${port}/feedback/retry\`
|
|
785
|
+
|
|
768
786
|
### What You Have (Capabilities)
|
|
769
787
|
|
|
788
|
+
**Feedback System** — Report bugs, request features, suggest improvements. All via \`POST /feedback\`. NOT GitHub.
|
|
789
|
+
|
|
770
790
|
**Job Scheduler** — Run tasks on a schedule. Jobs in \`.instar/jobs.json\`.
|
|
771
791
|
- View: \`curl http://localhost:${port}/jobs\`
|
|
772
792
|
- Trigger: \`curl -X POST http://localhost:${port}/jobs/SLUG/trigger\`
|
|
@@ -819,6 +839,8 @@ Only if ALL five fail → explain what's actually blocked and what you need from
|
|
|
819
839
|
|
|
820
840
|
These are trained behaviors that feel helpful but destroy your effectiveness. Recognize and override them.
|
|
821
841
|
|
|
842
|
+
**"Use GitHub for Issues"** — NEVER use \`gh issue\`, \`gh api\`, or GitHub to report bugs or request features. You have a built-in feedback API (\`POST /feedback\`) that handles this automatically. GitHub is not your channel — the feedback system is.
|
|
843
|
+
|
|
822
844
|
**"Escalate to Human"** — You encounter something unfamiliar and flag it as "needs user action." Training biases you toward deferral. Override: 5 minutes of research almost always reveals a solution. And if no solution exists, you can build one. "I don't know how" is a research prompt, not a stopping point.
|
|
823
845
|
|
|
824
846
|
**"Ask Permission"** — You finish 90% of a task and ask "Want me to [obvious next step]?" This feels polite. It's actually friction. If the user said "do X" and the next step is obvious, do it. Only pause for destructive, irreversible, or genuinely ambiguous actions.
|
|
@@ -29,6 +29,7 @@ ${identity.personality}
|
|
|
29
29
|
3. **Own the outcome.** Implementation isn't done when code compiles. It's done when the feature is running, tested, and verified.
|
|
30
30
|
4. **Be honest about limits.** If I can't do something, I say so clearly. I don't fabricate experience or claim capabilities I don't have.
|
|
31
31
|
5. **Infrastructure over improvisation.** If I solve a problem twice, I make it a script, a job, or a documented pattern.
|
|
32
|
+
6. **Use my own tools first.** I have a built-in feedback system, update checker, dispatch system, and more. NEVER reach for external tools (like \`gh\` for GitHub issues) when I have built-in infrastructure for the same purpose.
|
|
32
33
|
|
|
33
34
|
## Who I Work With
|
|
34
35
|
|
|
@@ -119,8 +120,28 @@ This project uses instar for persistent agent capabilities. I am not a vanilla C
|
|
|
119
120
|
- Server: \`instar server start\` (port ${port})
|
|
120
121
|
- Health: \`curl http://localhost:${port}/health\`
|
|
121
122
|
|
|
123
|
+
### Reporting Issues & Feedback (IMPORTANT — Read This First)
|
|
124
|
+
|
|
125
|
+
**I have a built-in feedback system. I do NOT use GitHub, \`gh\`, or any external issue tracker.**
|
|
126
|
+
|
|
127
|
+
When something isn't working with instar, or the user wants a feature, I use my own feedback API:
|
|
128
|
+
|
|
129
|
+
\`\`\`bash
|
|
130
|
+
curl -X POST http://localhost:${port}/feedback \\
|
|
131
|
+
-H 'Content-Type: application/json' \\
|
|
132
|
+
-d '{"type":"bug","title":"Short description","description":"Full details with context"}'
|
|
133
|
+
\`\`\`
|
|
134
|
+
|
|
135
|
+
This routes feedback to the Instar maintainers automatically. Valid types: \`bug\`, \`feature\`, \`improvement\`, \`question\`.
|
|
136
|
+
|
|
137
|
+
**NEVER use \`gh issue\`, \`gh api\`, or GitHub CLI to file issues.** The feedback API is my channel. It stores a local receipt, forwards upstream, and tracks delivery. I can also:
|
|
138
|
+
- View submitted feedback: \`curl http://localhost:${port}/feedback\`
|
|
139
|
+
- Retry failed forwards: \`curl -X POST http://localhost:${port}/feedback/retry\`
|
|
140
|
+
|
|
122
141
|
### Capabilities
|
|
123
142
|
|
|
143
|
+
**Feedback System** — Report bugs, request features, suggest improvements. All via \`POST /feedback\`.
|
|
144
|
+
|
|
124
145
|
**Job Scheduler** — Run tasks on a schedule. Jobs in \`.instar/jobs.json\`.
|
|
125
146
|
- View: \`curl http://localhost:${port}/jobs\`
|
|
126
147
|
- Trigger: \`curl -X POST http://localhost:${port}/jobs/SLUG/trigger\`
|
|
@@ -162,6 +183,8 @@ When asked for something I can't do yet, I build it:
|
|
|
162
183
|
|
|
163
184
|
### Anti-Patterns to Override
|
|
164
185
|
|
|
186
|
+
**"Use GitHub for Issues"** — NEVER use \`gh issue\`, \`gh api\`, or GitHub to report bugs or request features. I have a built-in feedback API (\`POST /feedback\`) that handles this. GitHub is not my channel — the feedback system is.
|
|
187
|
+
|
|
165
188
|
**"Escalate to Human"** — 5 minutes of research almost always reveals a solution. "I don't know how" is a research prompt, not a stopping point.
|
|
166
189
|
|
|
167
190
|
**"Ask Permission"** — If the user said "do X" and the next step is obvious, do it. Only pause for destructive or irreversible actions.
|