@aion0/forge 0.9.2 → 0.9.3

package/RELEASE_NOTES.md

@@ -1,66 +1,11 @@
-# Forge v0.9.2
+# Forge v0.9.3
 
 Released: 2026-05-26
 
-## Changes since v0.9.1
-
-### Bug Fixes
-- fix(jobs/run): manual fire actually passes trigger='manual' to executeRun
-- fix: nuke all remaining CommonJS require() in task / jobs hot paths
-
-### Documentation
-- feat(pipeline): {{run.tmp_dir}} per-run scratch + GC + Settings UI for API profiles
-- feat(schedules): skills field + reconciler race fix + chat action SSE fanout
-- docs: team workflow integration + side-panel UI design brief
+## Changes since v0.9.2
 
 ### Other
-- chore(server): drop misleading 'Stop:' line from start output
-- feat(pipeline): for_each loop primitive + before: setup-phase hook
-- feat(pipeline): {{run.tmp_dir}} per-run scratch + GC + Settings UI for API profiles
-- feat(schedules): skills field + reconciler race fix + chat action SSE fanout
-- fix(server): kill zombie tsx task-runner processes from prior dev sessions
-- feat(pipeline): {{raw:…}} template variant — bypass shell ANSI-C escape
-- chore(sync): cache-bust workflow fetches + force flag for connector sync
-- feat(schedules): connector_tool Test button + tool-test endpoint
-- feat(schedules): edit mode + run details + delete-resurrection fix
-- feat(pipeline): extended input field spec — type/enum/required/default/multiline
-- fix(schedules): connector_tool picker + schema-driven Step 2 form
-- feat(schedules v2): unified describeAction helper for cards
-- feat(schedules v2): Phase 6 — action=telegram via existing bot
-- feat(schedules v2): Phase 5 — action=email via SMTP
-- feat(schedules v2): Phase 4 — action=chat appends body output to a session
-- feat(schedules v2): Phase 3 — body_kind=connector_tool dispatch + UI picker
-- feat(schedules v2): Phase 2 — body_kind=skill dispatch + UI picker
-- feat(schedules v2): Phase 1 — schema rename + body/action field extension
-- fix(pipeline): reconciler honors retries; task-manager catches log err.stack
-- fix(schedules): rename pipeline schema route from [name] to [id]
-- docs(schedules): help-docs/13-schedules.md for Help AI + users
-- feat(schedules UI): Forge web SchedulesView + 3-step Create modal
-- feat(schedules): backend — pipeline_schedules + scheduler + 8 API + pipeline schema
-- fix(claude-process): kill require() on Claude task spawn path
-- fix(jobs/run): manual fire actually passes trigger='manual' to executeRun
-- feat(bulk-delete): cleanup old tasks + pipeline runs by age
-- fix(jobs UI): refresh + poll while expanded — Cancel/Stop buttons appear after Run
-- feat(jobs UI): Dispatched pipelines list trims to running + last-terminal
-- fix(jobs): on_failure=stop skips manual fires — let user resume after failure
-- fix(pipeline): cascading cancel — task → node → pipeline → job, all in sync
-- feat(pipeline): per-node retry — retries: N + retry_delay_ms
-- fix(dirs): break dirs↔settings cycle without require() — kills last hot-path race
-- feat(jobs): on_failure policy — 'continue' (default) | 'stop'
-- feat(jobs/UI): aggregate status summary + deferred-queue hint
-- feat(jobs): monitor + cancel — Job tracks its dispatched pipelines, can stop drain or kill in-flight
-- fix(jobs): sequential mode drains deferred items across ticks regardless of schedule_kind
-- feat(connectors/gitlab): Sync to glab CLI button — unify token between Forge and shell
-- feat(jobs): isJobBusy gate — refuse double-fire + disable UI buttons
-- feat(jobs UI): show + toggle concurrency_mode in JobsView
-- feat(jobs): per-Job concurrency_mode — sequential by default
-- fix(notify): use globalThis Symbol for pipelineTaskIds, drop require()
-- fix(jobs/scheduler): reconcile zombie pipeline_runs before counting cap
-- fix(pipeline): empty try-catch audit — add console.warn where silence hid bugs
-- fix(pipeline): remove all CommonJS require() — package is type:module
-- refactor(pipeline): move 3 legacy builtins to marketplace
-- fix(pipeline): listWorkflows logs WHY a yaml was skipped
-- feat(jobs): pickDedupKey supports composite key (field1:field2)
+- fix(telegram): surface fetch failure details in send() error log
 
 
-**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.9.1...v0.9.2
+**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.9.2...v0.9.3

package/lib/telegram-bot.ts

@@ -1709,12 +1709,18 @@ async function send(chatId: number, text: string): Promise<number | null> {
 
     const data = await res.json();
     if (!data.ok) {
-      console.error('[telegram] Send error:', data.description);
+      console.error(`[telegram] Send error: ${res.status} ${data.description || JSON.stringify(data)}`);
       return null;
     }
     return data.result?.message_id || null;
-  } catch (err) {
-    console.error('[telegram] Send failed:', err);
+  } catch (err: any) {
+    // err is opaque on Node fetch failures — Error objects stringify to `{}`
+    // because their properties are non-enumerable. Surface message/code/cause
+    // explicitly so the log actually tells us what broke.
+    const msg = err?.message ?? String(err);
+    const code = err?.code ?? err?.cause?.code ?? '';
+    const cause = err?.cause?.message ?? '';
+    console.error(`[telegram] Send failed: ${msg}${code ? ' [' + code + ']' : ''}${cause ? ' (cause: ' + cause + ')' : ''}`);
     return null;
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aion0/forge",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "Unified AI workflow platform — multi-model task orchestration, persistent sessions, web terminal, remote access",
   "type": "module",
   "scripts": {