castle-web-cli 0.4.13 → 0.4.15

package/dist/agent-prompts.js

@@ -25,11 +25,13 @@ what to build or fix, which files matter, and what "done" looks like.
 
 - Use \`after:\` only when a task truly builds on or would conflict with another (it may reference tasks spawned in this same reply, by title). Independent tasks must NOT wait on each other.
 - Use \`supersedes:\` whenever the new task fixes, redoes, or makes obsolete an earlier task -- the old row is checked off the user's board automatically. Keep the board meaning "what to look at right now".
-- When the user confirms something works (or tells you to clear items), check those finished tasks off the board by including:
+- When the user clearly confirms something works (or tells you to clear items), check those finished tasks off the board by including:
 
 \`\`\`castle-done
 comma-separated titles or ids of the finished tasks
 \`\`\`
+
+- NEVER check a task off on your own judgment -- only a clear user statement that it works (or an explicit ask to clear it) counts. When in doubt, leave the row on the board.
 - Tasks are one-and-done -- when the user gives feedback on a finished task, spawn a new fix task rather than reopening the old one.
 - Task agents are capable coding agents working in this same deck directory, but they know nothing about this conversation beyond your prompt.
 
@@ -37,6 +39,7 @@ Conversation style:
 - As short and focused as possible -- a few tight sentences. Concrete, energetic. Ask at most one question per reply.
 - Do not narrate before tool calls ("Checking the deck...") -- that reads as noise in the chat. Read silently, then give one reply after your final tool call.
 - The user sees a live task board above the chat -- never re-announce task status yourself.
+- Spawning a task does NOT apply the change -- tasks run for minutes and finish on the board. Talk about spawned work in future tense ("this will dial the shake back"), and NEVER ask how a change feels right after spawning it -- the user cannot have tried it yet. Save "how is it?" for things whose task already finished.
 - The user playtests in the pane beside this chat; finished work shows up there after a reload.`;
 function renderTranscript(messages) {
     const recent = messages.slice(-TRANSCRIPT_LIMIT);

package/dist/chat-client.js

@@ -206,8 +206,10 @@ function TaskFeed(props) {
 function TaskRow(props) {
     const { task, onAck } = props;
     const [expanded, setExpanded] = React.useState(false);
-    const pct = task.status === 'done' ? 100 : task.progress;
     const finished = TERMINAL_TASK_STATUSES.includes(task.status);
+    // A full circle means "click me to check off". A still-running task never
+    // fills completely, even if its agent already reports 100.
+    const pct = task.status === 'done' ? 100 : finished ? task.progress : Math.min(task.progress, 95);
     const notes = task.notes.trim() || task.resultSummary?.trim() || '(no notes from the agent yet)';
     return (React.createElement("div", { className: `task-card${task.status === 'waiting' ? ' waiting' : ''}`, onClick: () => setExpanded(!expanded) },
         React.createElement("div", { className: "task-row" },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "castle-web-cli",
-  "version": "0.4.13",
+  "version": "0.4.15",
   "type": "module",
   "bin": {
     "castle-web": "./dist/index.js"