@linxiraos/pi-utils 1.4.10 → 1.4.11

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## [Unreleased]
 
+## [1.4.11] - 2026-11-06
+
+- `applyLegacyOmpEnv()` lets a host apply the read-only legacy OMP dotenv files after its settings layer resolves the compatibility switch; the eager `ZETA_OMP_COMPAT` pass is unchanged.
+
 ## [1.4.10] - 2026-11-05
 
 - Legacy OMP dotenv files are no longer loaded by default; set `ZETA_OMP_COMPAT=1` to opt into the read-only fallback. Zeta `.zeta` dotenv files keep precedence.

package/THIRD-PARTY-NOTICES.txt

@@ -5,6 +5,50 @@ This generated, self-contained aggregate accompanies Zeta release artifacts.
 It does not replace package-level license files. First-party licensing grants
 no rights in third-party code, fonts, data, or marks identified below.
 
+ZETA IS A FORK AND REDISTRIBUTION
+=================================
+
+Zeta is a downstream distribution of oh-my-pi (OMP), and it also contains forks
+of OMP Web, OMP Studio and TermIDE. Upstream copyright notices stay with their
+files and are not restated here. This section states, for every forked or
+vendored application tree, where it came from, what Zeta changed, and why.
+Upstream URLs are the ones configured in `.git/config`; the per-tree deviation
+ledgers are authoritative for details.
+
+Forked application trees:
+
+| Path | Upstream | Snapshot | License | What Zeta changed |
+|---|---|---|---|---|
+| `packages/ main/ crates/ python/ lsp/ sdk/ types/ skills/` | oh-my-pi (OMP), https://github.com/can1357/oh-my-pi | integrated through tag `v18.15.0` (`document/upstream-sync.md`) | see upstream files | product name, paths, command names and env prefixes; branded assets; internal identifiers renamed to `__zeta*` |
+| `web-ui/` | OMP Web, https://github.com/17380936778/omp-web | frozen snapshot + manual cherry-picks (`document/upstream-sync.md`) | see upstream files | gateway transport, theme token bridge, page routing |
+| `web-app/` (`src/studio`, `src/vendor/*`) | OMP Studio 0.1.17, https://github.com/the-snowpear/omp-studio | `0.1.17`, ported into the product renderer | MIT | maintained by Zeta now: the host contract is reimplemented in `studio-host` (pair/CSRF/query/command/events), the renderer was rebranded (`zeta-studio` wire name, Zeta links/fixtures), and Zeta adds windowed transcripts, precompressed static serving, the plugin registry, and the usage dashboard |
+| `termide/` | TermIDE, https://github.com/termide/termide | tag `0.46.0` = `a027ca788cd4c9d24f060cdcd3195ca2e475617b` | MIT | deviations listed in `termide/VENDOR.md` (28 entries) |
+| `editor/npm/*` (`@linxiraos/editor*`) | TermIDE `panel-editor` | same tree as `termide/` | MIT | built as the editor-only bin `termide-editor` (`editor/npm/editor/VENDOR.md`) |
+| `plugins/official/*` | per plugin | per plugin | per plugin | each directory carries `plugin.json`, README with source, and its license |
+
+Why the fork renames things at all: the upstream licenses and the product
+identity both require that a downstream distribution not present itself as the
+upstream. Renames therefore cover the product name, command names
+(`zetawork` / `zetacode` / `zetaide`), the `zeta://` scheme, the npm scope
+`@linxiraos/*`, and release asset names (`zeta-cli-*`). User-visible
+configuration keeps accepting the legacy names during the transition, so an
+existing installation does not silently break.
+
+Brand and assets:
+
+* Product marks — name, logos, app icons, wordmarks, splash art — are Zeta's own
+  and are not redistributed from any upstream. Upstream marks are not shipped.
+* Assets that do come from an upstream are enumerated in the per-tree ledgers
+  above; each keeps its upstream license notice in place.
+
+Frozen counterpart constants (interoperability, not branding):
+
+* Stencil OIDC `client-id "omp"`, its issuer and scopes; `catalog.stencil.so`;
+  `docs.stencil.so/tern/protocol/`; `my.omp.sh` as the collaboration relay
+  constant; the `__omp_judgment_images` upload key. These are wire-compatible
+  identifiers Zeta must keep, listed here so that a brand sweep does not break
+  them.
+
 PYTHON DEPENDENCY DISTRIBUTION ROLE
 ===================================
 
@@ -385,6 +429,62 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
+-------------------------------------------------------------------------------
+web-app/src/studio + web-app/src/vendor/* + web-ui/components/studio +
+web-ui/styles/studio + web-ui/lib/studio-protocol
+
+Ported UI surface and protocol types from OMP Studio 0.1.17 (MIT).
+
+- `web-ui/components/studio/` and `web-ui/styles/studio/` are derived from the
+  OMP Studio renderer (`apps/renderer/src`).
+- `web-ui/lib/studio-protocol/` vendors the type and validation surface of
+  `@omp-studio/client-contract` and `@omp-studio/studio-protocol` (78 files, no
+  runtime dependency), so the ported renderer keeps its own read models.
+- `web-ui/lib/studio-client/` is Zeta's own implementation of the
+  `StudioClient` interface over the Zeta gateway; it is not derived from
+  `@omp-studio/client`.
+
+The data plumbing, transport and packaging are Zeta's own and are not part of
+that derivation.
+
+  Copyright (c) 2026 snowpear and OMP Studio contributors
+  Copyright (c) 2026 Linxira-OS and Zeta contributors (Zeta modifications and additions)
+
+Local modifications: the product renderer moved to `web-app/` (Vite 7) with
+its own node project, and the host contract is Zeta's `studio-host` rather than
+Studio's server. `@omp-studio/client-contract` and
+`@omp-studio/studio-protocol` imports were rewritten to the vendored copies in
+both trees; `@omp-studio/client` is replaced by `web-ui/lib/studio-client` (the
+frozen snapshot) and by the host-backed transport in `web-app/`. The wire
+protocol name is `zeta-studio`, the desktop bridge global is
+`zetaStudioChrome`, Studio's design tokens were rebound to Zeta's theme alias
+layer (`--studio-*` → `--zeta-alias-*`), and surfaces with no Zeta backend were
+dropped rather than ported. Zeta-only additions: windowed transcript
+pagination, precompressed static assets, the real plugin registry, the usage
+dashboard, and the brand sweep. The MIT notice above covers the unmodified
+upstream portions; Zeta's changes are additionally under
+`Copyright (c) 2026 Linxira-OS and Zeta contributors`.
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
 -------------------------------------------------------------------------------
 packages/coding-agent/src/export/html/vendor/NOTICE
 

package/dist/types/env.d.ts

@@ -45,6 +45,15 @@ export declare function getDotenvEnvValues(cwd?: string, env?: Record<string, st
  */
 export declare function parseEnvFile(filePath: string): Record<string, string>;
 export declare function isOmpCompatEnabled(env?: Record<string, string | undefined>): boolean;
+/**
+ * Apply the legacy OMP dotenv files on demand.
+ *
+ * The eager pass above only sees `ZETA_OMP_COMPAT` from the shell or a Zeta
+ * dotenv file. A host that resolves the persisted `compat.importLegacyOmp`
+ * setting calls this once its settings layer is loaded. Idempotent, and it
+ * never overwrites a name the process already has.
+ */
+export declare function applyLegacyOmpEnv(): void;
 /**
  * Intentional re-export of Bun.env.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@linxiraos/pi-utils",
-	"version": "1.4.10",
+	"version": "1.4.11",
 	"description": "Shared utilities for pi packages",
 	"keywords": [
 		"utilities",
@@ -54,8 +54,8 @@
 		"fmt": "oxfmt --no-error-on-unmatched-pattern 'src/**/*.{ts,tsx}' '{test,bench,examples,scripts}/**/*.ts' '*.ts'"
 	},
 	"dependencies": {
-		"@linxiraos/pi-natives": "1.4.10",
-		"@linxiraos/pi-omptype": "1.4.10"
+		"@linxiraos/pi-natives": "1.4.11",
+		"@linxiraos/zeta-schema": "1.4.11"
 	},
 	"devDependencies": {
 		"@types/bun": "1.4.4"

package/src/acp/schema.ts

@@ -1,4 +1,4 @@
-import { type Type, type } from "@linxiraos/pi-omptype";
+import { type Type, type } from "@linxiraos/zeta-schema";
 import type {
 	ForkSessionResponse,
 	LoadSessionResponse,

package/src/env.ts

@@ -326,7 +326,8 @@ const ompCompatValue =
 	agentEnv.ZETA_OMP_COMPAT ??
 	piEnv.ZETA_OMP_COMPAT ??
 	homeEnv.ZETA_OMP_COMPAT;
-const legacyOmpEnv = isOmpCompatEnabled({ ZETA_OMP_COMPAT: ompCompatValue }) ? loadLegacyOmpEnv() : {};
+const legacyOmpEnabled = isOmpCompatEnabled({ ZETA_OMP_COMPAT: ompCompatValue });
+const legacyOmpEnv = legacyOmpEnabled ? loadLegacyOmpEnv() : {};
 
 for (const key of Object.keys(Bun.env)) {
 	const value = Bun.env[key];
@@ -335,7 +336,8 @@ for (const key of Object.keys(Bun.env)) {
 	}
 }
 
-for (const file of [projectEnv, agentEnv, piEnv, homeEnv, legacyOmpEnv]) {
+/** Copy one dotenv file into the process environment; an already-set name wins. */
+function mergeDotenvIntoProcess(file: Record<string, string>): void {
 	for (const key in file) {
 		if (!isMacosMallocStackLoggingEnvName(key) && !Bun.env[key]) {
 			Bun.env[key] = file[key];
@@ -344,6 +346,8 @@ for (const file of [projectEnv, agentEnv, piEnv, homeEnv, legacyOmpEnv]) {
 	}
 }
 
+for (const file of [projectEnv, agentEnv, piEnv, homeEnv, legacyOmpEnv]) mergeDotenvIntoProcess(file);
+
 // Directory-affecting keys (XDG_*_HOME, and in default mode ZETA_CODING_AGENT_DIR)
 // may have just arrived from the profile/agent `.env` applied above. The dirs
 // resolver cached its paths at module load — before this file ran — so rebuild
@@ -351,6 +355,23 @@ for (const file of [projectEnv, agentEnv, piEnv, homeEnv, legacyOmpEnv]) {
 // the profile name + home, so this re-reads only the directory vars.
 refreshDirsFromEnv();
 
+let legacyOmpEnvApplied = legacyOmpEnabled;
+
+/**
+ * Apply the legacy OMP dotenv files on demand.
+ *
+ * The eager pass above only sees `ZETA_OMP_COMPAT` from the shell or a Zeta
+ * dotenv file. A host that resolves the persisted `compat.importLegacyOmp`
+ * setting calls this once its settings layer is loaded. Idempotent, and it
+ * never overwrites a name the process already has.
+ */
+export function applyLegacyOmpEnv(): void {
+	if (legacyOmpEnvApplied) return;
+	legacyOmpEnvApplied = true;
+	mergeDotenvIntoProcess(loadLegacyOmpEnv());
+	refreshDirsFromEnv();
+}
+
 /**
  * Intentional re-export of Bun.env.
  *