instar 1.3.1608 → 1.3.1609

package/dashboard/console/console.js

@@ -47,6 +47,8 @@ const expanded = new Set();             // cards the operator expanded; kept acr
 const openRows = new Set();             // rows the operator opened; kept across refreshes
 let rowSeq = 0;
 let homeChatId = null;
+// The agent-wide Attention topic, where every attention item is posted.
+let attentionTopicId = null;
 let homeRun = null;
 
 // ── tiny DOM helpers ──────────────────────────────────────────────────────
@@ -257,6 +259,8 @@ function actionHref(action) {
     return `#/work/promises?${params}`;
   }
   if (action.kind === 'topic') return topicLink(homeChatId, action.topicId);
+  if (action.kind === 'href') return action.href || null;
+  if (action.kind === 'attention') return attentionTopicId ? topicLink(homeChatId, attentionTopicId) : null;
   return null;
 }
 
@@ -449,7 +453,7 @@ function loadHome() {
     ? { ...model, retrying: true, line: [model.line, 'Checking again automatically.'].filter(Boolean).join(' ') } : model;
   const refresh = (key) => {
     const names = results.pool ? machineNames(results.pool) : {};
-    if ((key === 'attention' || key === 'pool') && results.attention) set('needs', annotate(buildNeeds(results.attention, Date.now(), names), results.attention));
+    if ((key === 'attention' || key === 'pool' || key === 'systemTopics') && results.attention) set('needs', annotate(buildNeeds(results.attention, Date.now(), names), results.attention));
     if ((key === 'sessions' || key === 'pool' || key === 'topics') && results.sessions) set('doing', annotate(buildDoing(results.sessions, Date.now(), names, topicNameMap(results.topics)), results.sessions));
     if (key === 'pool' && results.pool) set('running', annotate(buildRunning(results.pool), results.pool));
     if ((key === 'commitments' || key === 'pool') && results.commitments) {
@@ -472,6 +476,10 @@ function loadHome() {
         || key === 'topics' && ((result.data?.pool?.failed?.length || 0) > 0 || (result.data?.pool?.unresolved?.length || 0) > 0));
       const retryable = partial || (!result.ok && !['not signed in', 'switched off on this agent'].includes(result.reason));
       results[key] = partial ? { ...result, retrying: true } : result;
+      if (key === 'systemTopics' && result.ok) {
+        const t = Number(result.data?.topics?.attention);
+        attentionTopicId = Number.isFinite(t) && t > 1 ? t : null;
+      }
       if (key === 'pool' && result.ok) {
         const self = (result.data?.machines || []).find((m) => m.isSelf || m.machineId === result.data.selfMachineId);
         homeChatId = self?.servesChannels?.telegram?.chatIds?.[0] || null;
@@ -489,6 +497,7 @@ function loadHome() {
   // A slow source cannot block another card or start overlapping refreshes.
   read('pool', '/pool', POOL_TIMEOUT_MS);
   read('attention', '/attention?scope=pool', POOL_TIMEOUT_MS);
+  read('systemTopics', '/telegram/system-topics');
   read('sessions', '/sessions?scope=pool', POOL_TIMEOUT_MS);
   read('topics', '/telegram/topics?scope=pool', POOL_TIMEOUT_MS);
   read('commitments', '/commitments?scope=mesh', COMMITMENTS_TIMEOUT_MS);

package/dashboard/console/home-model.js

@@ -115,6 +115,23 @@ export function needsOperator(item) {
   return /decision|approval|review|sign-?in|relogin/i.test(cat);
 }
 
+/**
+ * Where the operator acts on an item. Every row in "needs you" gets one: its
+ * own conversation; the Desktop page for that machine; the Accounts page for a
+ * sign-in; otherwise the Attention topic, where the item was posted and can be
+ * answered.
+ */
+export function needAction(item) {
+  if (item && item.topicId != null && Number.isFinite(Number(item.topicId))) return { kind: 'topic', topicId: Number(item.topicId) };
+  const cat = String((item && item.category) || '');
+  if (/^desktop$/i.test(cat)) {
+    const q = item.machineId ? `?machineId=${encodeURIComponent(item.machineId)}` : '';
+    return { kind: 'href', href: `/dashboard/desktop.html${q}` };
+  }
+  if (/sign-?in|relogin/i.test(cat)) return { kind: 'href', href: '#/capacity/accounts' };
+  return { kind: 'attention' };
+}
+
 export const STALE_DAYS = 14;
 const DAY = 86400000;
 
@@ -154,7 +171,7 @@ export function buildNeeds(res, now = Date.now(), names = {}) {
       tone: stale ? 'unknown' : (top.priority === 'URGENT' ? 'bad' : 'attn'),
       detail: top.description || top.body || '',
       expandable: true,
-      action: Number.isFinite(Number(top.topicId)) ? { kind: 'topic', topicId: Number(top.topicId) } : null,
+      action: needAction(top),
     };
   }).sort((a, b) => Number(a.stale) - Number(b.stale) || a.prio - b.prio || b.last - a.last);
   const current = all.filter((g) => !g.stale);

package/dist/data/standards-guard-index.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "generatedFrom": "source-tree",
   "registrySha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
-  "packageVersion": "1.3.1608",
+  "packageVersion": "1.3.1609",
   "guards": [
     {
       "ref": "docs/audits/phase-b/f10-triage.md",

package/dist/data/standards-guard-index.meta.json

@@ -1,5 +1,5 @@
 {
-  "sha256": "f8a624d90b7e0da9279f067fef9e141bac4834e4418d71b592ef4c5b07b6af49",
+  "sha256": "ccaa1ee5b44efb04fe258136a20c35325729fa9683990dc4015d33d480a8b715",
   "registrySha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
-  "packageVersion": "1.3.1608"
+  "packageVersion": "1.3.1609"
 }

package/dist/data/standards-registry.meta.json

@@ -2,5 +2,5 @@
   "sha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
   "articleCount": 93,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1608"
+  "packageVersion": "1.3.1609"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.1608",
+  "version": "1.3.1609",
   "description": "Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.",
   "type": "module",
   "main": "dist/index.js",

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-11-02T20:00:15.797Z",
-  "instarVersion": "1.3.1608",
+  "generatedAt": "2026-11-02T20:33:29.976Z",
+  "instarVersion": "1.3.1609",
   "entryCount": 206,
   "entries": {
     "hook:session-start": {

package/src/data/standards-guard-index.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "generatedFrom": "source-tree",
   "registrySha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
-  "packageVersion": "1.3.1608",
+  "packageVersion": "1.3.1609",
   "guards": [
     {
       "ref": "docs/audits/phase-b/f10-triage.md",

package/src/data/standards-guard-index.meta.json

@@ -1,5 +1,5 @@
 {
-  "sha256": "f8a624d90b7e0da9279f067fef9e141bac4834e4418d71b592ef4c5b07b6af49",
+  "sha256": "ccaa1ee5b44efb04fe258136a20c35325729fa9683990dc4015d33d480a8b715",
   "registrySha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
-  "packageVersion": "1.3.1608"
+  "packageVersion": "1.3.1609"
 }

package/src/data/standards-registry.meta.json

@@ -2,5 +2,5 @@
   "sha256": "db01d9f92c6aa26ca903702896b41be53722982ed07d27633237bb254c214290",
   "articleCount": 93,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1608"
+  "packageVersion": "1.3.1609"
 }

package/upgrades/1.3.1609.md

@@ -0,0 +1,20 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+- Every item in the dashboard's "What needs you" card now links to where you act on it: its own conversation, the Desktop page for that machine, the Accounts page for a sign-in, or otherwise the Attention topic where it was posted. Before, items without a conversation were plain text.
+
+## What to Tell Your User
+
+Everything in "What needs you" is now a link. Tap an item and you land where you can deal with it, for example the remote-desktop setup for that exact machine.
+
+## Summary of New Capabilities
+
+None. This completes the existing "needs you" card.
+
+## Evidence
+
+- On a live agent, both items in "What needs you" (remote-desktop permission on two machines) showed as plain text with no link. On the preview, each now links to the Desktop page with that machine selected.

package/upgrades/side-effects/console-needs-you-links.eli16.md

@@ -0,0 +1,7 @@
+# Every item in "What needs you" now has a place to tap
+
+The dashboard's home screen has a card called "What needs you". It lists the things only you can do: approve something, sign in somewhere, or fix a setting on a machine. The rule we agreed is that everything in that list must come with a button or a link that takes you straight to where you act, because a request you cannot act on is just noise.
+
+Until now that rule was only half true. An item tied to a conversation linked to that conversation. Anything else (for example "Remote Desktop needs its Mac permission again" on the Mac Mini) was shown as plain text you could expand and read, with nowhere to go. That is what both items on the list looked like this morning.
+
+Now every item gets a destination. A remote-desktop item opens the Desktop page with that exact machine selected, where the step-by-step setup and the Retry button are. A sign-in item opens the Accounts page. Anything else opens the Attention conversation in Telegram, where that item was posted and where you can answer it. If the dashboard cannot work out where the Attention conversation is, the item falls back to readable text, never a broken link. Nothing is hidden or removed by this change; it only adds the missing links.

package/upgrades/side-effects/console-needs-you-links.md

@@ -0,0 +1,33 @@
+# Side-effects review: every "needs you" row has somewhere to act
+
+## Change
+`dashboard/console/home-model.js` adds `needAction(item)`; `buildNeeds` uses it for every row. Order: the item's own topic; a `desktop` item opens `/dashboard/desktop.html?machineId=<its machine>` (that page has the guided setup and Retry for that machine); a sign-in item opens Accounts; anything else opens the Attention topic in Telegram, where the item was posted. `dashboard/console/console.js` reads `GET /telegram/system-topics` once to learn the Attention topic and maps the new `href` and `attention` action kinds to links.
+
+Before, a row without a topic id rendered as expandable text with no link. On the Studio today both rows in "needs you" (Remote Desktop permission on Mac Lan and Mac Mini) were like that.
+
+## 1. Over-block
+None. Not a gate.
+
+## 2. Under-block
+If the Attention topic cannot be read, an `attention` row falls back to the old expandable text (no link). It never shows a broken link.
+
+## 3. Level-of-abstraction fit
+The console page model decides where a row links. Correct layer.
+
+## 4. Signal vs authority
+No decision point. Not applicable.
+
+## 5. Interactions
+A row with a link renders as a link instead of an expandable row, so its description is not shown inline; the destination (Desktop page, conversation, Attention topic) carries the full text. The headline now says "Tap to review and respond." for these items, as it already did for conversation items. The card still hides itself when there is exactly one actionable item, because the headline then links to it.
+
+## 6. External surfaces
+One extra read (`GET /telegram/system-topics`) per console load. It is read-only and already authenticated.
+
+## 6b. Operator-surface quality
+Checked on the preview: each of the two Remote Desktop rows links to the Desktop page with that machine selected.
+
+## 7. Multi-machine posture
+Items come from `/attention?scope=pool` and carry their machine id; the Desktop link uses the item's own machine. The Attention topic is the agent-wide system topic (one per agent). Machine-local page code.
+
+## 8. Rollback cost
+Revert the commit; no data or migration.