@corenel/cli 0.3.2 → 0.4.1

package/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor's trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising out
+of these terms or the use or nature of the software, under any kind of legal
+claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion of
+it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over, are
+under the control of, or are under common control with that organization.
+**control** means ownership of substantially all the assets of an entity, or the
+power to direct its management and policies by vote, contract, or otherwise.
+Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under these
+terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/README.md

@@ -21,13 +21,21 @@ Assistant replies render as markdown. More verbs (`run` / `ask` / `chat` /
 ## Releasing
 
 `@corenel/term` (the terminal face) is a real runtime dependency, not bundled
-into `dist/cli.js` -- see the note at the top of `build.mjs`. It therefore has
-to be published FIRST; publishing `@corenel/cli` against an unpublished
-`@corenel/term` yields a package that cannot install at all, so `npx
-@corenel/cli` fails before any verb runs.
+into `dist/cli.js` -- see the note at the top of `build.mjs`. `@corenel/term`'s
+own dist is bundled but keeps `@corenel/harness` and `@corenel/protocol`
+EXTERNAL (see `packages/term/build.mjs`) -- both the CLI and term import the
+harness directly, and they must resolve to the SAME installed copy, or the
+`llm-execution` feature guard and `--debug` logging silently apply to the
+wrong module instance. That makes all four packages real runtime dependencies
+of each other, and publish order matters:
 
-    pnpm --filter @corenel/term build && pnpm --filter @corenel/term publish
-    pnpm --filter @corenel/cli  build && pnpm --filter @corenel/cli  publish
+    pnpm --filter @corenel/protocol build && pnpm --filter @corenel/protocol publish
+    pnpm --filter @corenel/harness  build && pnpm --filter @corenel/harness  publish
+    pnpm --filter @corenel/term     build && pnpm --filter @corenel/term     publish
+    pnpm --filter @corenel/cli      build && pnpm --filter @corenel/cli      publish
+
+Publishing any package against an unpublished dependency yields one that
+cannot install at all, so `npx @corenel/cli` fails before any verb runs.
 
 Publish with **pnpm, never npm**: this CLI depends on `@corenel/term` as
 `workspace:*`, and pnpm rewrites the `workspace:` protocol to a real version at
@@ -36,4 +44,24 @@ workspace produces a manifest whose install fails with
 `EUNSUPPORTEDPROTOCOL / Unsupported URL Type "workspace:"`, which is the very
 breakage this section exists to prevent.
 
+**All four versions must be bumped and published together, in the order
+above, every release -- even one that only touches a single package.** pnpm
+rewrites every `workspace:*` dependency to the EXACT current version of that
+dependency at pack time. All four packages are pinned to the same harness
+version today, so a normal `npm install` of `@corenel/cli` resolves to one
+harness copy. Bump `@corenel/harness` and publish a new `@corenel/term`
+without also republishing `@corenel/cli`, and the tree that installs
+`@corenel/cli` gets the OLD harness version nested under it (frozen into the
+manifest `@corenel/cli` published against) plus the NEW harness version
+hoisted at the top level for `@corenel/term` -- two separate harness module
+instances again, silently. That is exactly the bug this section's ordering
+exists to prevent (see `harnessSingleInstance.test.ts` in this package's
+`test/`): `registerGuard()`/`setAgentLogging()` calls made through one
+instance configure a module the other never reads, so the `llm-execution`
+feature gate silently stops running and `--debug` logging can't be turned
+off. Every test in this repo stays green when that happens, because the
+in-repo workspace is symlinked (one instance by construction) and the
+build-output regression test only exercises that same symlinked layout --
+neither one can see a real, version-skewed `npm install`.
+
 Licensed under Elastic-2.0.