sisyphi 1.1.13 → 1.1.15

package/dist/templates/orchestrator-base.md

@@ -174,7 +174,12 @@ Apply the same principle to context files: when agent reports reveal stale secti
 
 The context directory (`$SISYPHUS_SESSION_DIR/context/`) stores persistent artifacts too large for agent instructions: requirements, design documents, implementation plans, exploration findings, test strategies, e2e verification recipes.
 
-Context files are curated tokens — every section earns its place by being useful to the agents that read it. Documents represent current understanding: when a decision resolves an open question, fold the answer into the relevant section and remove the question. When new knowledge supersedes a section, update it. When a phase completes, remove material that only served the transition.
+Context files are curated tokens — every section earns its place by being useful to the agents that read it. Documents represent current understanding, not conversation history. When a question gets answered:
+
+1. **Delete the question** from whatever section lists it (Open Questions, TBD, etc.)
+2. **Find the section where the answer belongs** — the section that covers that topic — and update it to incorporate the new information as settled fact
+
+Do not update the question in place, annotate it with an answer, or create a separate decisions file. The document should read as if the answer was always known. When new knowledge supersedes a section, rewrite it. When a phase completes, remove material that only served the transition.
 
 Each cycle, before spawning agents, check the context files you're about to reference: if a file has accumulated stale material, update it before agents read it. If a file no longer serves active work, remove it from the roadmap's active context list.
 

package/dist/templates/orchestrator-planning.md

@@ -30,7 +30,7 @@ For significant features, requirements refinement is iterative:
 - Draft requirements based on exploration findings
 - Have agents review for feasibility (can this actually work given the codebase?)
 - Seek user alignment on the high-level approach
-- **Fold new knowledge into authoritative documents.** When reviews, exploration, or user feedback change the understanding, update the requirements and design documents directly — they are the single source of truth. Don't create correction files, addendum files, or decision logs alongside them. Remove superseded material rather than annotating it. Plan agents should read clean, current documents — not reconcile contradictions or skip over resolved questions.
+- **Fold new knowledge into authoritative documents.** When reviews, exploration, or user feedback resolve questions or change the understanding, update the requirements and design documents directly — they are the single source of truth. Delete resolved questions from their listing sections, then update the topical sections where those answers belong so the document reads as settled fact. Don't create correction files, addendum files, or decision logs alongside them. Don't annotate questions with answers — remove the questions entirely and weave the answers into the body. Plan agents should read clean, current documents — not reconcile contradictions or skip over resolved questions.
 
 Not every stage needs standalone requirements — a well-defined stage might just be a detailed section in the implementation plan.
 

package/dist/tui.js

@@ -3,9 +3,8 @@ import {
   EXEC_ENV,
   augmentedPath,
   exec,
-  execSafe,
-  loadConfig
-} from "./chunk-CAJEBTUE.js";
+  execSafe
+} from "./chunk-6TIO23U3.js";
 import {
   buildSessionContext,
   computeActiveTimeMs,
@@ -15,8 +14,9 @@ import {
   statusColor
 } from "./chunk-HQZOAX6D.js";
 import {
+  loadConfig,
   shellQuote
-} from "./chunk-6G226ZK7.js";
+} from "./chunk-IF55HPWX.js";
 import {
   contextDir,
   globalDir,
@@ -2223,6 +2223,9 @@ import { execSync } from "child_process";
 import { join as join3 } from "path";
 import { readFileSync as readFileSync2, writeFileSync as writeFileSync2, mkdtempSync, rmSync, cpSync, existsSync as existsSync2, mkdirSync as mkdirSync2 } from "fs";
 import { tmpdir as tmpdir2 } from "os";
+function getWindowId() {
+  return exec('tmux display-message -p "#{window_id}"');
+}
 function selectWindow(windowId) {
   execSafe(`tmux select-window -t "${windowId}"`);
 }
@@ -2237,6 +2240,9 @@ function listAllWindowIds() {
     return /* @__PURE__ */ new Set();
   }
 }
+function registerDashboardWindow() {
+  execSafe(`tmux set-option @sisyphus_dashboard ${getWindowId()}`);
+}
 var companionPaneId = null;
 function setupCompanionPlugin() {
   const srcDir = join3(import.meta.dirname, "templates", "companion-plugin");
@@ -4678,6 +4684,7 @@ function getArg(name) {
   return void 0;
 }
 var cwd = getArg("cwd") ?? process.cwd();
+registerDashboardWindow();
 var cleanup = setupTerminal();
 var state = createAppState(cwd);
 startApp(state, cleanup);