@house365/comate 0.2.1 → 0.2.3

package/bin/init-run.mjs

@@ -1,11 +1,12 @@
 // The `init` flow: install whatever the current project is missing.
-import { existsSync } from 'node:fs';
+import { existsSync, readFileSync } from 'node:fs';
 import { join, resolve } from 'node:path';
 
 import {
   MIN_OPENSPEC,
   NPM_TIMEOUT_MS,
   SKILLS_TIMEOUT_MS,
+  capture,
   npmInvocation,
   openSpecState,
   run,
@@ -147,6 +148,67 @@ function report(results) {
     console.error(`\n${failed.length} 项失败，修好后重跑 comate init。`);
     return 1;
   }
-  console.log('\n完成。在 agent 中输入 /comate 开始使用，或跑 comate doctor 自检。');
+  console.log(banner(pkgVersion()));
+  console.log('在 agent 中输入 /comate 开始使用，或跑 comate doctor 自检。\n');
   return 0;
 }
+
+// ponytail: read package.json rather than hardcoding — npm version bumps the
+// file, and a stale literal in the banner is worse than no version at all.
+export function pkgVersion(root = resolve(import.meta.dirname, '..')) {
+  try {
+    return JSON.parse(readFileSync(join(root, 'package.json'), 'utf8')).version;
+  } catch {
+    return '';
+  }
+}
+
+// Box-drawing glyphs need a UTF-8 capable terminal. Windows consoles still
+// default to a legacy codepage where they render as mojibake, so the wordmark
+// only goes out when the codepage says otherwise; everything else gets the
+// plain line.
+//
+// isTTY deliberately does NOT gate this. npm's Windows global install resolves
+// `comate` to a comate.ps1 shim, and PowerShell calling node through a .ps1
+// wrapper takes over stdout — so isTTY is false in a real terminal and the
+// wordmark never showed. CI is the case actually worth suppressing, and it
+// announces itself with an env var.
+export function banner(version, { utf8 = unicodeSafe(), ci = isCI() } = {}) {
+  const tag = `comate${version ? ` v${version}` : ''}`;
+  const plain = `\n  ${tag} - AI coding almost there!\n`;
+  if (!utf8 || ci) return plain;
+
+  const art = [
+    ' ██████╗ ██████╗ ███╗   ███╗ █████╗ ████████╗███████╗',
+    '██╔════╝██╔═══██╗████╗ ████║██╔══██╗╚══██╔══╝██╔════╝',
+    '██║     ██║   ██║██╔████╔██║███████║   ██║   █████╗  ',
+    '██║     ██║   ██║██║╚██╔╝██║██╔══██║   ██║   ██╔══╝  ',
+    '╚██████╗╚██████╔╝██║ ╚═╝ ██║██║  ██║   ██║   ███████╗',
+    ' ╚═════╝ ╚═════╝ ╚═╝     ╚═╝╚═╝  ╚═╝   ╚═╝   ╚══════╝',
+  ];
+  const cyan = (s) => (process.env.NO_COLOR ? s : `\x1B[36m${s}\x1B[0m`);
+  const dim = (s) => (process.env.NO_COLOR ? s : `\x1B[2m${s}\x1B[0m`);
+  return [
+    '',
+    // Trailing padding keeps the source rows aligned; strip it so the colour
+    // reset doesn't sit behind spaces the terminal may highlight on select.
+    ...art.map((line) => `  ${cyan(line.replace(/\s+$/, ''))}`),
+    '',
+    `  ${dim(`${tag} - AI coding almost there!`)}`,
+    '',
+  ].join('\n');
+}
+
+// POSIX terminals are UTF-8 in practice. Windows consoles are not: the legacy
+// codepage (936, 437, …) renders box-drawing glyphs as mojibake, so ask chcp
+// and only claim UTF-8 on 65001.
+function unicodeSafe() {
+  if (process.platform !== 'win32') return true;
+  return /65001/.test(capture('chcp', []) ?? '');
+}
+
+// Every major CI sets CI=true; GITHUB_ACTIONS covers the Actions runner even in
+// the odd config that doesn't.
+function isCI() {
+  return Boolean(process.env.CI || process.env.GITHUB_ACTIONS);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@house365/comate",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "comate —— OpenSpec + Superpowers 规约驱动的 AI 开发编排器（Agent Skills）",
   "type": "module",
   "license": "MIT",