@convilyn/sdk-author 0.7.0

package/CHANGELOG.md

@@ -0,0 +1,280 @@
+# Changelog
+
+All notable changes to `@convilyn/sdk-author` are documented here. The format
+follows [Keep a Changelog](https://keepachangelog.com/); this package adheres to
+[Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.7.0] — 2026-07-09
+
+### Fixed
+
+- **README licence corrected to Apache-2.0** (it claimed MIT; the shipped
+  `LICENSE` file, `package.json`, and the Python SDKs are all Apache-2.0).
+  `publishConfig.access: public` is now pinned in `package.json` so a manual
+  publish of this scoped package cannot accidentally target restricted access.
+
+### Added
+
+- **Hosted Author Runtime ported from the Python SDK.**
+  `ConvilynClient` gains `deployHostedRuntime(manifest, {region,
+  workflowSpec?})`, `rollbackHostedRuntime(runtimeId)`, and
+  `getHostedRuntimeLogs(runtimeId, {since?, limit?})` (accepts both the bare
+  list and `{entries}` envelope). The CLI `deploy` is un-gated: `deploy
+  --hosted [--region]` provisions the managed runtime (501/503 answer with the
+  BYO `push --endpoint-url` fallback hint; without `--hosted` it exits 1
+  pointing at `push`), and new `rollback <runtimeId>` / `logs <runtimeId>
+  [--since --limit]` commands complete the lifecycle. The old exit-2 hard gate
+  is gone.
+- New exported types: `PUBLIC_SCHEMA_VERSION`, `WorkflowBlueprint`,
+  `BlueprintAgentConfig`, `BlueprintMcpConfig`, `ExportPayload`,
+  `RuntimeStatus`, `DeployHostedRequest`/`DeployHostedResponse`,
+  `RollbackResponse`, `RuntimeLogEntry`.
+- **`ConvilynClient` rejects a consumer `ck_` key at construction** with a
+  precise `ConvilynAuthorError`, instead of the developer portal answering with
+  an opaque 401 later. The Author SDK authenticates with a `cvl_` developer key;
+  an empty key (register() mints one) and any non-`ck_` prefix are still
+  accepted (forward-compat). Mirror of the consumer SDKs' inverse guard.
+- **`convilyn-author push` is now wired to the Developer Portal.** It was
+  previously an operator-gated stub. It now loads a built server + a compiled
+  workflow, then submits both through `ConvilynClient` (`submitServer` →
+  `submitWorkflow`, threading the new server id into the workflow) — mirroring
+  the Python SDK's `ConvilynClient.push`. Requires `--endpoint-url
+  <https://...>` (the HTTPS URL where you host the server) and a `cvl_` key in
+  `CONVILYN_API_KEY`. New `--workflow-file` accepts a `workflow.spec.json` or a
+  built module exporting a `WorkflowSpec`.
+
+### Changed
+
+- **BREAKING: `WorkflowSpec.compile()` now emits the snake_case
+  `WorkflowBlueprint`** (`public_schema_version` / `spec_id` / `version` /
+  `keywords` / `agent_config` / `mcp_config`), in cross-SDK parity with the
+  Python author SDK — this is the shape the Developer Portal's
+  `submit_workflow` accepts, closing the always-422 publish break.
+  `WorkflowSpec` gains `specId` (required for `compile()`; constructor option
+  or `withSpecId()`) and a semver `version` (default `1.0.0`, `withVersion()`).
+  The camelCase user_workflows `ExportPayload` moved to `toExportPayload()` /
+  `WorkflowSpec.fromExportPayload()` (rename of `fromWire`); `fromJson()` /
+  `load()` shape-sniff and accept both file formats. The exported
+  `CompiledWorkflowSpec` type now aliases `WorkflowBlueprint`.
+- **BREAKING: `ConvilynClient` now targets the Developer Portal
+  (`/api/v1/developers/*`) with a `cvl_` developer key, not the first-party
+  console surfaces.** The previous client called `/user_workflows/*` +
+  `/mcp/tools/catalog` — all JWT/session endpoints owned by the web UI — with a
+  `CONVILYN_API_KEY` those endpoints reject (auth was structurally broken). It
+  now mirrors the Python `convilyn-author` SDK: `register` (mint a `cvl_` key),
+  `submitServer` / `listServers` / `serverStatus` / `testServer` /
+  `deactivateServer`, and `submitWorkflow` / `listWorkflows` / `workflowStatus`
+  / `testWorkflow` / `deactivateWorkflow`. Removed the first-party methods
+  `validate` / `import` / `fork` / `costPreview` / `toolCatalog` (and the gated
+  `patch` / `submitManifest`) — validate and cost-preview your work **locally**
+  with `runComplianceChecks` / `WorkflowSpec.compile` before submitting; the SDK
+  no longer consumes the platform MCP catalog. Removed the `/user_workflows` +
+  MCP-catalog wire types; added the snake_case Developer Portal types.
+- **Default platform URL corrected to `https://api.convilyn.corenovus.com`**
+  (was the non-serving `api.convilyn.com`), aligning every SDK's zero-config
+  default with the live API host.
+
+### Removed
+
+- **Dead `buildValidateRequest` / `buildCostPreviewRequest` exports** (and the
+  `requests.ts` module + its types). They built request bodies for
+  `POST /user_workflows/{validate,cost-preview}` — first-party console endpoints
+  the client stopped calling in the Developer-Portal rewrite. Validate +
+  cost-preview your work locally with `runComplianceChecks` / `WorkflowSpec.compile`.
+
+### Security
+
+- **10 MB inbound body cap on `POST /mcp`** — the runtime now stops buffering
+  and answers `413 PAYLOAD_TOO_LARGE` as soon as the inbound body crosses
+  10 MB, *before* signature verification, closing a pre-auth memory-exhaustion
+  vector on self-hosted servers. Parity with the Python / Go author runtimes'
+  shared cap.
+- **Confirmation-token digests keep `__proto__`-named argument keys.** The
+  canonicalizer previously built plain objects, so a `__proto__` /
+  `constructor`-named argument key was silently dropped from the digest —
+  diverging from the Python reference and letting that one key change between
+  confirmation and re-call without a digest mismatch. Canonicalization now
+  uses null-prototype accumulators; reserved names survive as ordinary keys.
+- **Fail-closed startup contract (pre-publish hardening).**
+  `serve()` now throws `ConvilynStartupError` when no HMAC secret is
+  configured and insecure local dev has not been explicitly opted into
+  (previously it booted a server that 401'd every `/mcp` call — safe but a
+  broken dev loop and divergent from the Python/Go UX). Opt-in is
+  `allowInsecure: true` (passed by `convilyn-author dev`) or
+  `CONVILYN_DEV_INSECURE=1`; in that mode unsigned `/mcp` requests are served
+  with a loud startup warning. A configured secret always wins — the opt-in
+  never bypasses verification. New public exports: `ConvilynStartupError`,
+  `ENV_DEV_INSECURE`, `devInsecureRequested`.
+
+## [0.6.0] — 2026-06-29
+
+### Added
+
+- **Docs & examples.** Expanded the README with `ConvilynClient`,
+  confirmation-token, local-harness (`invokeTool`), and authentication sections,
+  and a runnable `examples/quickstart` tool server.
+
+### Notes
+
+- **npm publish is operator-gated.** The release workflow (OIDC npm Trusted
+  Publisher, now the shared `.github/workflows/sdk-publish.yml`) fires only on
+  a `sdk-author-ts/v*` tag and is otherwise inert. Publishing requires the
+  one-time Trusted-Publisher registration + pushing that release tag — both
+  operator actions; this SDK lane does not publish.
+
+## [0.5.0] — 2026-06-29
+
+### Added
+
+- **`ConvilynClient`** (fetch-based) over the platform author endpoints.
+  Base = `${platformUrl}/api/v1`; auth = `Authorization: Bearer
+  <CONVILYN_API_KEY>`; `fetch` is injectable; no new runtime dependency.
+  Defined endpoints:
+  - `validate(spec | request)` → `POST /user_workflows/validate`
+  - `import(spec)` → `POST /user_workflows/import` (body = `spec.compile()`)
+  - `fork({ sourceSpecId, name? })` → `POST /user_workflows/fork`
+  - `costPreview(request)` → `POST /user_workflows/cost-preview`
+  - `toolCatalog()` → `GET /mcp/tools/catalog`
+  - Non-2xx responses throw `ConvilynApiError` (`status`, `body`).
+- **Gated (no contract → no network):** `patch()` (PATCH /user_workflows/{id} is
+  prose-only, not a defined operation) and `submitManifest()` (no
+  server-registration endpoint exists) throw with a message naming the gap — the
+  SDK-side counterpart of the CLI's gated `push`/`deploy`. No path is invented.
+- **`invokeTool(server, name, args, opts?)`** — a local testing harness that
+  drives `ToolServer.dispatch` in-process and returns the ToolResult wire
+  envelope, so authors can unit-test tools (incl. validation/tool-error paths)
+  without an HTTP server.
+- Platform wire types (`UserWorkflow`, `ForkRequest`, `McpToolCatalogResponse`,
+  `McpToolCatalogItem`, `McpServer`, `RiskLevel`), mirroring the contracts.
+
+## [0.4.0] — 2026-06-29
+
+### Added
+
+- **Confirmation-handshake token signing** (`mintConfirmationToken` /
+  `verifyConfirmationToken`), byte-for-byte compatible with the platform
+  gateway and the Python / Go author SDKs (verified by a cross-impl parity test
+  pinning a Python-reference-generated golden token):
+  - Token wire format `base64url("<expires>:<digest>:<sig>")` (url-safe, padding
+    kept); `digest = sha256(canonicalJson(normalizeForDigest(args)))`;
+    `sig = hmacSha256("<toolName>|<expires>|<digest>")`.
+  - `canonicalJson` matches Python `json.dumps(sort_keys=True,
+    separators=(",",":"))` with `ensure_ascii` (code points ≥ 0x80 → `\uXXXX`).
+  - `normalizeForDigest` strips volatile presigned-URL params before hashing,
+    re-encoding kept params with `quote_plus` semantics, so a re-presigned URL
+    still matches the confirmed arguments.
+  - `verifyConfirmationToken` strips the `confirmation_token` argument before
+    re-digesting, checks expiry, and constant-time-compares digest + signature;
+    raises `ConfirmationInvalidError` (reasons `malformed` / `expired` /
+    `digest_mismatch` / `signature_mismatch`).
+  - `CONFIRMATION_TTL_SECONDS = 300`; `SDKConfig.toolConfirmationSecret` reads
+    `CONVILYN_TOOL_CONFIRMATION_SECRET`. `node:crypto` only — no new dependency.
+  - This is a **distinct** scheme from the inbound request HMAC (`<timestamp>.<body>`
+    in `verifySignature`); the two are not interchangeable. The two-stage
+    `needs_confirmation` dispatch flow and `cost_*` envelope fields remain out of
+    scope.
+
+## [0.3.0] — 2026-06-29
+
+### Added
+
+- **The `convilyn-author` CLI** (`bin`, built to `dist/cli.cjs` via a new
+  tsup `cli` entry; commander-based). Subcommands:
+  - `init <name> [--dir]` — scaffold a TypeScript tool-server project
+    (`server.ts`, `package.json`, `tsconfig.json`, `.gitignore`, `.env.example`,
+    `README.md`); refuses a non-empty target directory.
+  - `synth [--file] [--output]` — load the built server module and write its
+    `ConvilynManifest` (default `convilyn.manifest.json`).
+  - `dev [--file] [--host] [--port]` — start the local JSON-RPC `/mcp` runtime
+    (`serve`).
+  - `test [--file]` — run the local compliance suite and exit non-zero on any
+    failure.
+  - `push` / `deploy` — **operator-gated stubs**. The platform
+    developer/server-registration API was not yet a published contract, so
+    there was no contract to bind them to; they report the gate (exit code 2)
+    and make no network calls. Real submission lands with the `ConvilynClient`
+    in a later release.
+
+  The CLI loads the author's server by dynamically importing a **built JS** module
+  (default `server.js`) and duck-types the export (the binary bundles its own
+  `ToolServer`, so `instanceof` across the install boundary is unreliable). The
+  `bin` is intentionally NOT part of the library `exports` map — library
+  consumers never pull in `commander`.
+- **`runComplianceChecks(server)`** — a library export producing a
+  `ComplianceReport` (metadata, tools-exist, tool-schemas, manifest-synth,
+  ref_id pattern, `get_tool_data`). The first producer of the existing
+  `ComplianceReport` type; reused by the CLI `test` command and seeds the
+  local harness. Author tool handlers are not blindly invoked.
+
+## [0.2.0] — 2026-06-29
+
+### Added
+
+- **`ToolServer` + JSON-RPC `/mcp` runtime.** A TS-authored server is now
+  runnable and interchangeable with the Python / Go author SDKs behind the same
+  gateway:
+  - `defineTool` — declare a tool from a **Zod** schema. The schema is the single
+    source of truth: `zod-to-json-schema` derives the manifest `input_schema`
+    (`additionalProperties:false`, matching Pydantic), `z.infer` types the handler
+    args, and the runtime validates inbound `/mcp` arguments against it. `zod` is a
+    peerDependency and is **not** re-exported (`import { z } from 'zod'`).
+  - `ToolServer` — tool registry (duplicate-name guard) + a transport-free
+    `dispatch()` for `tools/call`; produces the `ConvilynManifest`. Built-in
+    `get_tool_data` resolves an offloaded `ref_id` (not listed in the manifest).
+  - `serve` — Node `http` runtime: `GET /health`, `GET /manifest`, and
+    HMAC-verified `POST /mcp` (signature over the raw body bytes; bad signature →
+    `401 INVALID_SIGNATURE`, bad JSON → `400`).
+  - The snake_case ToolResult wire envelope (`summary` / `status` /
+    `data` / `ref_id` / `validation_errors` / `error` + legacy `success` /
+    `error_code` / `error_message` mirrors), with >16 KB `ok` payloads offloaded
+    to the `DataStore` as a `ref_id`.
+  - `ToolResult.ok` / `.fail` gain an optional trailing `summary` (the original
+    shapes are preserved exactly when it is omitted).
+- The two-stage `needs_confirmation` handshake and `cost_micro_u` /
+  `cost_breakdown` reporting are intentionally deferred to a follow-up.
+
+## [0.1.0] — 2026-06-27
+
+### Added
+
+- Initial foundation scaffold of the TypeScript Author SDK (a faithful
+  port of the Python `convilyn_sdk` and the Go `convilyn-author-go`).
+- HMAC inbound verification + signer (`verifySignature` / `signRequest`) — wire
+  format `<timestamp>.<body>`, headers `x-convilyn-signature` / `-timestamp`
+  (server-id audit-only), constant-time comparison, 300s replay tolerance, and
+  coarse `InvalidSignatureError` reasons. Byte-for-byte compatible with the
+  gateway signer and the Python / Go author SDKs (covered by a cross-impl parity
+  test).
+- The in-memory data store (`InMemoryDataStore`, `generateRefId` → `td_<12-hex>`,
+  `createDataStore`); the production-grade persistent store lands later.
+- `ConvilynManifest` — the compiled tool-server blueprint: camelCase domain →
+  snake_case wire (empty lists kept as `[]`), with `toJson` / `save` / `load` /
+  `fromJson`.
+- `SDKConfig` (environment-driven, `CONVILYN_*`), the `ToolContext` execution
+  context + `ProgressBackend` / `ConsoleProgressBackend`, and the core value
+  types (`ToolResult` / `ToolError` / `ToolDataRef` / `ToolSpec` / `ServerSpec` /
+  `ComplianceResult` / `ComplianceReport`).
+- Packaging discipline: an exact public-surface allowlist, an internal-token leak
+  scan, an `exports`-map-only-`.` assertion, and version ↔ CHANGELOG lockstep.
+  tsup ESM + CJS + type-declaration build; vitest ≥ 80% coverage gate.
+- **Workflow authoring** (grounded in the platform's published contracts,
+  not a port):
+  - `WorkflowSpec` — an immutable fluent builder for the portable authoring
+    artifact. `with*` / `add*` / `useTools` return a new spec; `compile()` emits
+    the `ExportPayload` **camelCase** shape (name / description / systemPrompt /
+    toolPalette / tags / canvasLayout); `compileJson` / `save` / `fromJson` /
+    `load` round-trip. Enforces the contract constraints client-side (name ≤80,
+    description ≤500, systemPrompt ≤8000, ≤20 tools, ≤8 tags, and rejects the
+    `request_user_input` tool).
+  - The five `WorkflowPolicies` types (`RetryPolicy` / `TimeoutPolicy` /
+    `OutputValidationPolicy` / `HumanReviewPolicy` / `FallbackPolicy`) + a
+    range-validating `buildWorkflowPolicies`.
+  - Typed request bodies + pure builders for the authoring helper endpoints:
+    `buildValidateRequest` and `buildCostPreviewRequest` (the HTTP client lands
+    in a later increment).
+
+The platform client, docs/examples, and the npm-publish workflow followed in
+the subsequent releases above. The `needs_confirmation` handshake +
+`cost_micro_u` / `cost_breakdown` support remain planned work.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 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 accept (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 2026 CoreNovus contributors
+
+   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.