mercury-composable 4.12.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2018-2026 Accenture.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,195 @@
+# Mercury Composable — polyglot functions for Node.js
+
+Write decoupled functions in JavaScript/TypeScript and let
+[Mercury Composable](https://github.com/Accenture/mercury-composable) engines (Java, and the
+official [Rust port](https://github.com/Accenture/mercury)) orchestrate them from Event Script
+flows and MiniGraph knowledge graphs — with no orchestration code in Node.js at all.
+
+This package is a deliberately **lightweight wrapper of the Event-over-HTTP protocol**:
+
+- an **Event API host** (`POST /api/event`) that dispatches incoming event envelopes to your
+  registered functions,
+- a **thin client** (`PostOffice`) to call functions on peer applications the same way,
+- the **standard event envelope wire format** codec (language-neutral MsgPack), and
+- a **primitive in-process event bus** — the single dispatch pipeline: one FIFO mailbox
+  per route consumed by `instances` worker loops, and
+- the **minimalist utilities** shared with the engines for consistency: configuration
+  management, logging in the engines' presentation format, and distributed-trace context.
+
+Orchestration deliberately stays in the engines. Functions written here are addressed by
+route name through the engines' declarative `yaml.event.over.http` map, so a flow or a
+graph task calls a Node.js function exactly as if it were local.
+
+**Documentation:** <https://accenture.github.io/mercury-nodejs/> — including the
+[AI Agent Guide](https://accenture.github.io/mercury-nodejs/guides/ai-agent-guide/)
+for deterministic function generation.
+
+> **Status: pre-release.** This repository was repurposed in August 2026 for the polyglot
+> initiative: instead of re-porting the full composable foundation to Node.js, the fresh
+> start rides the engines' Event-over-HTTP protocol — light by design. The previous
+> Node.js port (up to v4.3.28) remains available in the git history and on npm.
+
+## Quick start
+
+```javascript
+// app.mjs
+import { AppException, platform, preload } from 'mercury-composable';
+
+preload('hello.node', { instances: 10 }, async (headers, body) => {
+  if (typeof body !== 'object' || body === null || !('text' in body)) {
+    throw new AppException(400, "missing 'text'");
+  }
+  return { text: String(body.text).toUpperCase(), language: 'node.js' };
+});
+
+await platform.run(); // port from rest.server.port (default 8085)
+```
+
+Run it:
+
+```bash
+npm install && npm run build
+node dist/src/cli.js app.mjs -Drest.server.port=8087     # or: mercury-serve app.mjs -Drest.server.port=8087
+```
+
+Call it from a Mercury engine application with two configuration entries and no code —
+`application.properties`:
+
+```properties
+yaml.event.over.http=classpath:/event-over-http.yaml
+```
+
+`event-over-http.yaml`:
+
+```yaml
+event.http:
+  - route: 'hello.node'
+    target: 'http://127.0.0.1:8087/api/event'
+```
+
+Any Event Script task or MiniGraph `graph.task` node that names the route `hello.node`
+now executes the Node.js function, with trace context carried end to end.
+
+## The function contract
+
+A handler receives the same two-part input as an engine `TypedLambdaFunction` —
+`(headers, body)` — and returns the reply body (or an `EventEnvelope` for full control of
+status and reply headers). Node.js is non-blocking by nature; handlers may be async.
+
+- Throw `AppException(status, message)` for intentional errors — it becomes the portable
+  error contract on the wire (envelope status + message), handled by the calling flow's
+  exception handler or the graph's `error.*` contract.
+- `getTrace()` exposes `traceId` / `tracePath` / `cid`; `annotateTrace(k, v)` sends an
+  annotation back on the reply envelope.
+- Functions must be stateless; anything you must keep belongs to the caller's flow model
+  or state machine.
+
+### Local function calls
+
+`PostOffice` **without an endpoint** delivers through this application's own event bus —
+the engines' semantics for an in-app `po` call:
+
+- `isPrivate: true` means exactly what it means in the engines: callable **in-app only**.
+  Local calls reach private and public routes alike; the HTTP host keeps answering 403
+  for private targets from the wire.
+- `instances` is faithful: each route has one FIFO mailbox consumed by that many worker
+  loops. RPC waits are bounded by `timeoutMs` (the standard 408 envelope on breach), and
+  a queued call whose caller already timed out is skipped, never wastefully executed.
+- There is **no spill tier and no queue cap** by design: back-pressure belongs to the tier
+  that owns recovery — the engines' flows and graphs. A leaf host fails fast by deadline
+  instead of hoarding work.
+
+Local eventing is for simple leaf-side composition. Workflow processing belongs in Event
+Script and Knowledge Graph on the engines — that boundary is the architecture.
+
+## Configuration, logging, telemetry
+
+The same conventions as the engines, so a polyglot installation stays uniform:
+
+| Key | Meaning | Default |
+|-----|---------|---------|
+| `application.name` | application identity in logs | `application` |
+| `rest.server.port` | Event API port | `8085` |
+| `log.format` | `text`, `json` (pretty-printed) or `compact` (single-line JSONL) | `text` |
+| `log.level` | log level (`LOG_LEVEL` env var wins) | `INFO` |
+
+Configuration lives in the `resources` folder, mirroring the engines:
+`resources/application.yml` (or `.yaml` / `.properties`) in the working directory or next
+to the application file, or an explicit `--config` path — see
+[`examples/resources/application.yml`](examples/resources/application.yml) for a worked
+sample. Values support `${ENV_VAR:default}` substitution. Runtime parameter overrides use the
+same `-D` syntax as the Java engine and the Rust port — checked first on every read
+(`appConfig().set(key, value)` does the same programmatically, the `f:setConfig` analog):
+
+```bash
+mercury-serve app.mjs -Drest.server.port=8087 -Dlog.format=json
+```
+
+Log lines follow the Java reference engine's pattern for one-aggregation consistency:
+
+```text
+2026-08-22 10:15:30.123 INFO  app:12 - Loaded PUBLIC hello.node, instances=10
+```
+
+## Actuator endpoints
+
+The host serves the engines' operational endpoints on the same port as `/api/event`, so
+Kubernetes probes and dashboards treat a Node.js app exactly like a Java or Rust engine app:
+
+| Endpoint | Purpose |
+|----------|---------|
+| `GET /` | minimal index page linking the endpoints below |
+| `GET /info` | app identity, runtime, origin id, start time, uptime |
+| `GET /info/routes` | registered routes split by visibility, with instance counts |
+| `GET /env` | selected environment variables and configuration parameters |
+| `GET /health` | dependency health checks — `UP` (HTTP 200) or `DOWN` (HTTP 400) |
+| `GET /livenessprobe` | `OK` while the last health outcome was good, else HTTP 400 |
+
+Configuration keys carry the engines' names: `info.app.version`, `info.app.description`,
+`show.env.variables` and `show.application.properties` (opt-in lists — secrets are never
+dumped wholesale), and `mandatory.health.dependencies` / `optional.health.dependencies`
+(routes of health check functions; optional ones never change the overall status). A
+health check function is a normal registered function — usually private — speaking the
+engines' interface contract, called through the event bus:
+
+```javascript
+preload('demo.health', { isPrivate: true }, async (headers, _body) => {
+  if (headers.type === 'info') {
+    return { service: 'demo.service', href: 'http://127.0.0.1' };
+  }
+  return 'demo.service is running fine';   // a non-200 reply marks it down
+});
+```
+
+JSON responses are pretty-printed — the engines' default-serializer presentation — and
+unknown paths answer the engines' error shape
+(`{"status": 404, "message": "Resource not found", "type": "error"}`).
+
+Kubernetes wiring: point `livenessProbe` at `/livenessprobe` and `readinessProbe` at
+`/health`.
+
+## Wire compatibility
+
+The codec implements the
+[Event Envelope Wire Format](https://accenture.github.io/mercury-composable/guides/event-envelope-wire-format/)
+(standard format) and is verified against the golden conformance vectors shared by the
+Java and Rust engines (`test/vectors/vectors.json`). The classic compact format is
+detected and rejected with a teaching error — engines default to the standard format for
+Event over HTTP.
+
+Serialization notes: 64-bit integers beyond `Number.MAX_SAFE_INTEGER` decode as `BigInt`
+(exact), smaller ones as `number`; timestamps travel as ISO-8601 UTC strings with
+millisecond precision; binary payloads are `Uint8Array`.
+
+## Scope
+
+This package intentionally contains **no orchestration: no flows, no graphs, no
+persistence, no pub/sub broadcast** — those live in the engines. What it does carry is
+deliberately minimal: functions, a primitive in-process event bus (route mailboxes +
+workers, RPC and drop-n-forget — nothing more), and the minimalist foundation utilities,
+keeping Node.js fast to prototype with while the composable core guarantees the
+architecture.
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE).

package/dist/src/actuator.d.ts

@@ -0,0 +1,36 @@
+import * as http from 'node:http';
+import { FunctionRegistry } from './registry.js';
+/**
+ * Unique instance id, minted once per process (the Java reference engine's
+ * format: UTC yyyyMMdd date prefix + 32-hex uuid).
+ */
+export declare function appOrigin(): string;
+/**
+ * Human-readable duration matching the engines' rendering (including their
+ * strict boundary behavior, kept verbatim for parity).
+ */
+export declare function elapsedTime(milliseconds: number): string;
+/** The engines' host-level error shape (SimpleHttpUtility signature). */
+export declare function sendError(res: http.ServerResponse, status: number, message: string): void;
+/** HTTP handlers for the actuator endpoints (wired by EventApiServer). */
+export declare class Actuator {
+    private readonly registry;
+    private readonly start;
+    private healthy;
+    private readonly appName;
+    private readonly appVersion;
+    private readonly description;
+    private readonly required;
+    private readonly optional;
+    constructor(registry: FunctionRegistry);
+    /** Route a GET to its actuator endpoint; false when the path is not ours. */
+    handle(pathname: string, res: http.ServerResponse): Promise<boolean>;
+    private appBlock;
+    private info;
+    private routes;
+    private env;
+    private health;
+    private checkServices;
+    /** Probe one health-check function; false when it is missing or down. */
+    private checkService;
+}