@gotcos/glasses-server 6.37.0 → 6.37.1

package/.env.example

@@ -182,12 +182,17 @@ BIND_HOST=0.0.0.0
 # WITHOUT the COS operations pipeline (no COS_SCRIPTS_DIR). Spawns one
 # `claude -p --model haiku` per meeting, at the end of finalization.
 #
-# Default OFF. With it off you still get the deterministic tier — speakers,
-# talk-time, word count, opening excerpt — which costs nothing and always runs.
+# Default ON since 6.37.0. Set to 0 to opt out; only a literal 0 disables.
+# With it off you still get the deterministic tier — speakers, talk-time, word
+# count, opening excerpt — which costs nothing and always runs.
+#
+# This spends tokens on YOUR provider plan, unlike the display toggles. It is
+# bounded by a per-day cap (below) counted only on a validated summary, a
+# circuit breaker, a minimum word floor, a single-slot queue and a wall budget.
 #
 # Never runs when COS_SCRIPTS_DIR is set: overwriting the summary section would
 # erase the markers sync_meetings.py uses to decide what to process.
-# COS_MEETING_SUMMARY=1
+# COS_MEETING_SUMMARY=0
 #
 # Calls per local day before the summariser falls back to the deterministic
 # tier for the rest of the day. Default 40.

package/CHANGELOG.md

@@ -1,3 +1,27 @@
+## 6.37.1
+
+Standalone meeting summaries default ON.
+
+6.37.0 shipped everything else in this release — the honest summary slot, the
+two enrichment tiers, the voice-profile name validator, and Continue threads /
+video uploads / adaptive audio cleanup all defaulting on — but it went out with
+COS_MEETING_SUMMARY still defaulting OFF. That meant the headline fix, a meeting
+that comes back with a real summary, reached nobody unless they found an
+undocumented environment variable.
+
+Only a literal '0' disables, so a stray or malformed value cannot silently
+switch summaries off.
+
+This is a different class of default from the display toggles in 6.37.0: it
+spends tokens on the USER'S OWN provider plan. Every control in the module is
+load-bearing rather than decorative — a per-day cap counted only on a validated
+summary, a circuit breaker with its own accounting, a minimum word floor, a
+single-slot queue, and a wall budget that keeps finalization under COS Control's
+90s restart proof.
+
+No other change. Anyone already on 6.37.0 who set COS_MEETING_SUMMARY=1 by hand
+is unaffected.
+
 ## 6.37.0
 
 Meetings recorded without the COS operations pipeline now get a real summary,
@@ -64,8 +88,11 @@ Two enrichment tiers, both standalone-only:
               with talk-time split, opening excerpt. Fabricates nothing:
               topics/decisions/actions come back empty rather than guessed.
 
-  llm         COS_MEETING_SUMMARY=1, default OFF. One `claude -p --model haiku`
-              per meeting at the ops_pending phase of finalization.
+  llm         DEFAULT ON. One `claude -p --model haiku` per meeting at the
+              ops_pending phase of finalization. Set COS_MEETING_SUMMARY=0 to
+              opt out; only a literal 0 disables. This spends tokens on the
+              USER'S OWN provider plan, which is why every control below is
+              load-bearing rather than decorative.
 
 It runs at ops_pending specifically because batch HQ transcription replaces the
 whole transcript; summarising earlier would describe text the file no longer
@@ -79,7 +106,7 @@ erase them and the pipeline would skip the meeting entirely -- losing domain
 reclassification, task extraction and the operations copy.
 
 COST CONTROLS
-  - COS_MEETING_SUMMARY, read live (not frozen at module load)
+  - COS_MEETING_SUMMARY, read live (not frozen at module load), default ON
   - haiku pinned explicitly, so it can never inherit an Opus session default
   - own daily cap (COS_MEETING_SUMMARY_DAILY_CAP, default 40), never shared
     with the archive counter; committed only after a validated summary, so a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gotcos/glasses-server",
-  "version": "6.37.0",
+  "version": "6.37.1",
   "description": "COS Glasses — self-hosted AI heads-up-display server for Even G2 smart glasses, powered by Claude Code, Codex, or Cursor Agent CLI",
   "type": "module",
   "bin": {

package/server/lib/meeting-summary.ts

@@ -87,10 +87,19 @@ export const meetingSummaryBreaker = breaker
 
 /** Read LIVE, not at module load. COS Control rebuilds the runtime plist
  *  environment on update, and tests flip this per-case; a module-scope const
- *  would freeze the value at import and make both untestable. */
+ *  would freeze the value at import and make both untestable.
+ *
+ *  DEFAULT ON since 6.37.0 (Miles 2026-08-25). Shipping this off meant the
+ *  headline fix — a meeting that comes back with a real summary — reached
+ *  nobody unless they found an undocumented env var.
+ *
+ *  Unlike the display toggles that flipped on in the same release, this one
+ *  spends tokens on the USER'S OWN provider plan, which is why every control in
+ *  this module is load-bearing: a per-day cap committed only on a validated
+ *  result, a breaker with its own accounting, a minimum word floor, a
+ *  single-slot queue, and a wall budget. Only a literal '0' disables. */
 export function meetingSummaryLLMEnabled(): boolean {
-  const raw = process.env.COS_MEETING_SUMMARY?.trim()
-  return raw === '1' || raw?.toLowerCase() === 'true'
+  return process.env.COS_MEETING_SUMMARY?.trim() !== '0'
 }
 
 // ── Transcript parsing ──────────────────────────────────────