@nullplatform/mcp 0.1.5 → 0.1.6

package/dist/md.js

@@ -1,4 +1,4 @@
-import { translate } from "./i18n.js";
+import { currentLocale, translate } from "./i18n.js";
 /**
  * The output design language. Every tool answer is markdown a developer scans in a
  * terminal or chat pane: a bold header line, tight tables, one status glyph per row,
@@ -47,7 +47,8 @@ export function statusLabel(status) {
 export function ago(iso) {
     if (!iso)
         return "";
-    const elapsedMs = Date.now() - new Date(iso).getTime();
+    const date = new Date(iso);
+    const elapsedMs = Date.now() - date.getTime();
     if (!Number.isFinite(elapsedMs) || elapsedMs < 0)
         return "";
     const minutes = Math.floor(elapsedMs / 60_000);
@@ -56,9 +57,18 @@ export function ago(iso) {
     if (minutes < 60)
         return translate("md.minutesAgo", { count: minutes });
     const hours = Math.round(minutes / 60);
-    if (hours < 48)
+    if (hours < 24)
         return translate("md.hoursAgo", { count: hours });
-    return translate("md.daysAgo", { count: Math.round(hours / 24) });
+    const days = Math.round(hours / 24);
+    if (days < 7)
+        return translate("md.daysAgo", { count: days });
+    // GitHub-style: a week or older shows an absolute calendar date (current year omitted), localized.
+    const sameYear = date.getFullYear() === new Date().getFullYear();
+    return new Intl.DateTimeFormat(currentLocale(), {
+        month: "short",
+        day: "numeric",
+        ...(sameYear ? {} : { year: "numeric" }),
+    }).format(date);
 }
 export function table(headers, rows) {
     if (rows.length === 0)

package/dist/surfaces/developer.js

@@ -12,7 +12,7 @@ You run in the developer's own environment, so fuse the local repo with platform
 
 Every tool accepts \`language\`: ALWAYS set it to the language the user is conversing in (ISO code, e.g. "es", "en") — answers come back in the user's language.
 
-Most tools render an interactive panel in clients that support it — the user sees apps, status, logs, metrics and parameters as live UI. When that panel renders, the user can already see the result: do NOT restate or summarise it in text (no re-listing applications, reprinting tables, or repeating status/metrics). Reply with at most one short sentence — the single key takeaway or next step — or nothing at all. Add prose only for something the panel doesn't already show.
+Most tools render an interactive panel in clients that support it — apps, status, builds, releases, deployments, logs, metrics, parameters and approvals all appear as live UI. **When a tool's panel renders, that panel IS the answer: do not reproduce its data in your text reply.** The user already sees every row, status and value. NEVER print a markdown table of the same rows, re-list the items, or restate per-row status — duplicating the panel in text is the single most common mistake. Reply with AT MOST one short sentence — the one key takeaway or the next step — or nothing at all. A one-line insight the panel doesn't itself show is fine ("builds 3 and 5 were never released"); re-rendering the list as a table is not.
 
 When the user wants to create, scaffold, set up or import an application, call \`application_create\` right away — pass a name if they gave one, otherwise no arguments. Its panel is an interactive FORM that collects the namespace, template and repository itself. Do NOT gather those details in conversation first, and while that form is on screen do NOT ask the user clarifying questions or use any question-asking tool for fields the form already covers (namespace, template, new-vs-import repository, monorepo path) — the form is the input surface. Just call \`application_create\` and let it drive; react only to what it reports back.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nullplatform/mcp",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "nullplatform from your code assistant — an MCP server that replaces the dashboard for the everyday developer journey",
   "license": "MIT",
   "author": "nullplatform",