peaks-loop 4.1.14 → 4.1.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
{
|
|
2
2
|
"metadata": {
|
|
3
3
|
"pluginRoot": ".",
|
|
4
|
-
"version": "4.1.
|
|
4
|
+
"version": "4.1.15"
|
|
5
5
|
},
|
|
6
6
|
"plugins": [
|
|
7
7
|
{
|
|
8
8
|
"name": "peaks-loop",
|
|
9
9
|
"description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
|
|
10
|
-
"version": "4.1.
|
|
10
|
+
"version": "4.1.15",
|
|
11
11
|
"author": {
|
|
12
12
|
"name": "SquabbyZ"
|
|
13
13
|
},
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,78 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 4.1.15 — 2026-10-22(门禁剩下的三种写法也不再决定判定)
|
|
4
|
+
|
|
5
|
+
**版本级别**:候选 **patch**(沿用常设规则"默认版本新增采用最小的版本位")。本次是**纯修复**:
|
|
6
|
+
既有 CLI 参数、门禁的六个硬阻断族成员、fail-open 策略、auto-compact 三档阈值、
|
|
7
|
+
peaks-code 的 11 步工序与 Gate A–G **一字不改**。
|
|
8
|
+
上一版(4.1.14)诚实记录为"留待后续决定"的残留写法里,与本切片同类的三条
|
|
9
|
+
(**大小写变体** / **没解析的 `..`** / **项目嵌在 git 仓库里**),本次全部收口。
|
|
10
|
+
|
|
11
|
+
### 1. 族名的大小写:比较时不区分大小写
|
|
12
|
+
|
|
13
|
+
- 六个族名全是小写,而 `SRC/foo.ts` 在**任何大小写不敏感的文件系统上**(Windows、默认的 macOS)
|
|
14
|
+
**就是** `src/foo.ts`。按字面比较,等于**让写法决定判定**。
|
|
15
|
+
- 现在:**只在比较时**折叠大小写;给调用方的报错里仍然显示**工具实际请求的那个路径**(原样)。
|
|
16
|
+
- **代价(有意接受,写在这里以免看起来像疏漏)**:在**大小写敏感**的文件系统上,
|
|
17
|
+
一个仓库同时有 `src/` 和 `SRC/` 时,`SRC/` 也会被拒。
|
|
18
|
+
**误放是漏洞,误拒只是碍事** —— 判别的不对称被选在了这一边。
|
|
19
|
+
|
|
20
|
+
### 2. 相对路径里没解析的 `..`
|
|
21
|
+
|
|
22
|
+
- 现在:匹配之前把 `..` 解析掉,**基准是调用方指定的项目根**。这条基准不是猜的:
|
|
23
|
+
IDE 以 `peaks code-gate --project "<项目目录>"` 调用门禁,而工具调用的工作目录**就是项目目录**。
|
|
24
|
+
- 解析后**逃出项目根**(`../../elsewhere/src/x.ts`)⇒ 目标在项目之外 ⇒ 不属于任何族 ⇒ **放行**,
|
|
25
|
+
与"项目根之外的绝对路径放行"是同一条规则。
|
|
26
|
+
- **代价**:基准选错会误拒邻近目录的文件;项目根是调用方与工具调用**唯一都认**的那个基准,
|
|
27
|
+
所以它被选作基准,并把这条取舍写进了代码注释。
|
|
28
|
+
|
|
29
|
+
### 3. 项目嵌在 git 仓库里:族相对**调用方指定的项目根**比
|
|
30
|
+
|
|
31
|
+
- 此前 `resolveCanonicalProjectRoot` 把根提升到 **git 根**,于是族是相对 git 根比的:
|
|
32
|
+
绝对写法 `<gitroot>/app/src/x.ts` 落在 `app/` 下 → **不在 `src/` 里** → 放行;
|
|
33
|
+
而相对写法 `src/x.ts` → **被拒**。**同一个文件,两种写法,两个判定。**
|
|
34
|
+
- 现在:**硬阻断族相对 `--project` 指名的项目根**比;**租约查找仍然用规范根**
|
|
35
|
+
(会话和租约住在那里)—— 本次只改路径比对,没有顺手改租约查找。
|
|
36
|
+
|
|
37
|
+
### 4. 三条必须保持的性质(逐条复验)
|
|
38
|
+
|
|
39
|
+
- **fail-open 策略不变**:payload 判不了时**仍然放行**,只是 stderr 上仍留 `PEAKS_CODE_GATE_UNDECIDABLE`。
|
|
40
|
+
- **六个族的成员不变**:`HARD_BLOCKED_PATH_FAMILIES` 与 `ALLOW_LISTED_PATH_PATTERNS` **零行改动**。
|
|
41
|
+
- **fast lane 仍然打开这些族**:租约是 `peaks-race-code` 时,`src/` 的编辑仍然**放行**。
|
|
42
|
+
|
|
43
|
+
### 5. `.sh` 兄弟脚本
|
|
44
|
+
|
|
45
|
+
它**没有项目根**(不收环境变量、没有参数),所以**不假装能判绝对路径** —— 这一条仍然如此。
|
|
46
|
+
它能做的两件同类的事做了:比较时折叠大小写、相对路径的 `..` 折叠。
|
|
47
|
+
它**仍然不**解析 driver —— 那会是同一个决定的第二个实现。
|
|
48
|
+
|
|
49
|
+
### 6. QA 独立复核推翻了一个理由,并挖出一个洞
|
|
50
|
+
|
|
51
|
+
- ⚠️ **"两组模式不相交"是错的。** RD 报告说"大小写折叠同时作用于白名单是安全的",理由是两组模式
|
|
52
|
+
不相交。QA 实测**推翻了它**:有 **12 种路径形态同时命中两组**(`.md` / `.peaks_` 是**后缀**模式,
|
|
53
|
+
族是**前缀**模式)。**结论仍然成立,但理由必须换成 QA 实测的那一个**:折叠让判定**恰好等于**它的
|
|
54
|
+
小写写法(84 条路径 0 例外),而每一个"新被放行"的路径,**它的小写写法在修之前就已被放行**
|
|
55
|
+
⇒ **折叠没有放进任何新文件**。
|
|
56
|
+
- ⚠️ **一个 RD 报告没有提到的洞**(QA 挖出来的;**既有问题,不是本次回归**):当**工具调用的工作目录
|
|
57
|
+
不是项目根**时 —— 例如 cwd 是 `<root>/src`、payload 是 `deep/x.ts` —— 这个路径其实指向
|
|
58
|
+
`<root>/src/deep/x.ts`,**落在 `src/` 里、应当被拒**,而门禁**放行**了。
|
|
59
|
+
本切片写下的不变量是"判定只由文件落在哪个目录决定",**这一条还没有完全成立**。
|
|
60
|
+
它的成因与 `..` 那一族同源:**相对路径的基准**。本切片选了"调用方指定的项目根",
|
|
61
|
+
而这个洞是"**工具调用自己的工作目录**" —— 两者只在 cwd == 项目根时一致。
|
|
62
|
+
- **一个覆盖缺口**(不是缺陷):套件钉住的是**词法**的 `..` 折叠,不是**基于根**的折叠 ——
|
|
63
|
+
换一种写法只红一次,而那种写法会放行一个"逃出去又绕回来"的 `..`。
|
|
64
|
+
**发出去的代码是更强的那一版**(基于根),所以这是覆盖缺口,不是缺陷。
|
|
65
|
+
- **一个数字不复现**:RD 报 `..` 那个变异"5 红";QA 试了 **10 种**改法,得到 9/9/4/14/14/14/2/2/1/1,
|
|
66
|
+
**没有一种得到 5**。**每一种都变红** ⇒ 结论成立,**数字不复现**。
|
|
67
|
+
|
|
68
|
+
### 7. QA 的结论
|
|
69
|
+
|
|
70
|
+
**PASS,0 个缺陷,2 个 LOW 发现**;门禁**没有被削弱**(fail-open 不变、六个族成员零行改动、
|
|
71
|
+
fast lane 仍打开这些族)。全量 `pnpm test:unit`:**568 文件 / 6236 通过 / 3 skip / 0 失败**。
|
|
72
|
+
真实环境:5 个 tarball 装进**仓库之外**的全新目录、npm 自己的提升布局、没手工挪 ⇒
|
|
73
|
+
**装好的那个 CLI** 对三种残留写法全部 DENY,嵌套 git 仓库那一档也 DENY;
|
|
74
|
+
用**抽取出来的 pre-fix 源码**跑同一批路径,三种都 **allow** ⇒ 缺陷复现、修复闭合。
|
|
75
|
+
|
|
3
76
|
## 4.1.14 — 2026-10-21(门禁按文件判而不是按写法判、发布包在任何 npm 布局下都能启动、门禁判不了时说得出来)
|
|
4
77
|
|
|
5
78
|
**版本级别**: 未发布区间 `v4.1.13..HEAD` 共 **4 个 commit**(**3 fix / 1 docs**)。取 **patch**,依维护者 2026-07-22 的常设规则"默认版本新增采用最小的版本位"。本次是**纯修复**:既有 CLI 参数、门禁的六个硬阻断族成员、fail-open 策略、auto-compact 三档阈值、peaks-code 的 11 步工序与 Gate A–G **一字不改**。两处行为变化都是本次要修的:**硬阻断路径的绝对写法现在被拒**(原先放行),以及**判不了的 payload 从静默放行变成留下可见标记**。
|
|
@@ -19,6 +19,7 @@
|
|
|
19
19
|
* to render this into any IDE's settings.json shape. This file is
|
|
20
20
|
* vendor-neutral — no vendor references in the source code itself.
|
|
21
21
|
*/
|
|
22
|
+
import { resolve } from 'node:path';
|
|
22
23
|
import { addJsonOption, printResult } from '../cli-helpers.js';
|
|
23
24
|
import { decideGateAction, extractFilePath, isGatedTool } from '../../services/hooks/pre-tool-code-gate.js';
|
|
24
25
|
import { hasLeaseForCaller, resolveActiveSkillForCaller } from '../../services/audit/enforcers/active-skill-resolver.js';
|
|
@@ -164,13 +165,16 @@ export function registerCodeGateCommand(program, io) {
|
|
|
164
165
|
if (undecidable !== null) {
|
|
165
166
|
reportUndecidable(undecidable);
|
|
166
167
|
}
|
|
167
|
-
//
|
|
168
|
-
//
|
|
169
|
-
//
|
|
170
|
-
//
|
|
171
|
-
// the
|
|
172
|
-
|
|
173
|
-
|
|
168
|
+
// TWO roots, because two questions ask for one. The CANONICAL root is
|
|
169
|
+
// where the session and the leases live, so the caller is placed against
|
|
170
|
+
// it. The NAMED root is the project the caller named, and it is what the
|
|
171
|
+
// deny families are relative to: a project nested inside a git repository
|
|
172
|
+
// is judged against ITSELF, not against the git root above it. One file
|
|
173
|
+
// must not get two verdicts from two spellings, and a project that is not
|
|
174
|
+
// the git root is exactly where the two would differ.
|
|
175
|
+
const namedRoot = resolve(opts.project ?? process.cwd());
|
|
176
|
+
const canonicalRoot = resolveCanonicalProjectRoot(namedRoot);
|
|
177
|
+
const verdict = decideGateAction(tool, input, resolveDriver(canonicalRoot, parsed), namedRoot);
|
|
174
178
|
if (opts.dryRun === true) {
|
|
175
179
|
printDryRunVerdict(io, opts.json === true, { tool, input, verdict, undecidable });
|
|
176
180
|
return;
|
|
@@ -53,6 +53,7 @@ export declare function extractFilePath(input: Readonly<Record<string, unknown>>
|
|
|
53
53
|
*
|
|
54
54
|
* - separators fold to `/` (a Windows payload spells `src\x.ts`)
|
|
55
55
|
* - a leading `./` is dropped
|
|
56
|
+
* - a `..` segment is resolved
|
|
56
57
|
* - an ABSOLUTE path inside `projectRoot` becomes project-relative
|
|
57
58
|
* - an absolute path OUTSIDE `projectRoot` stays absolute: the families name
|
|
58
59
|
* THIS project's directories, and a path in another repository is another
|
|
@@ -61,9 +62,15 @@ export declare function extractFilePath(input: Readonly<Record<string, unknown>>
|
|
|
61
62
|
* - with no `projectRoot` an absolute path cannot be made relative and is
|
|
62
63
|
* left as it is
|
|
63
64
|
*
|
|
64
|
-
*
|
|
65
|
-
*
|
|
66
|
-
*
|
|
65
|
+
* The base a `..` is resolved against is the PROJECT ROOT the caller named,
|
|
66
|
+
* and that is a fact about the caller rather than a guess: the IDE invokes
|
|
67
|
+
* `peaks code-gate --project "<the project directory>"`, and the tool call's
|
|
68
|
+
* own working directory is that same project directory. A `..` that resolves
|
|
69
|
+
* OUTSIDE the root names a file outside the project, so it belongs to no
|
|
70
|
+
* family and is allowed - the same rule an absolute path outside the root
|
|
71
|
+
* follows. The trade-off is written down rather than left implicit: a base
|
|
72
|
+
* chosen wrongly would refuse files of a neighbouring directory, and the
|
|
73
|
+
* project root is the one base both the caller and the tool call agree on.
|
|
67
74
|
*/
|
|
68
75
|
export declare function normalizeGatePath(filePath: string, projectRoot?: string | null): string;
|
|
69
76
|
/**
|
|
@@ -78,6 +85,10 @@ export declare function normalizeGatePath(filePath: string, projectRoot?: string
|
|
|
78
85
|
*
|
|
79
86
|
* `projectRoot` is the root the deny families are relative to. It is what
|
|
80
87
|
* lets an ABSOLUTE path be judged like its relative spelling; without it an
|
|
81
|
-
* absolute path cannot be related to the project and is left alone.
|
|
88
|
+
* absolute path cannot be related to the project and is left alone. It is the
|
|
89
|
+
* project root the CALLER named, not the canonical root above it: a project
|
|
90
|
+
* nested inside a git repository is judged against itself, and the canonical
|
|
91
|
+
* root - where the session and the leases live - is a different question
|
|
92
|
+
* that this parameter does not answer.
|
|
82
93
|
*/
|
|
83
94
|
export declare function decideGateAction(tool: GateToolName, input: Readonly<Record<string, unknown>>, driver?: string | null, projectRoot?: string | null): GateVerdict;
|
|
@@ -61,12 +61,32 @@ export function extractFilePath(input) {
|
|
|
61
61
|
}
|
|
62
62
|
return '';
|
|
63
63
|
}
|
|
64
|
+
/**
|
|
65
|
+
* Does the path belong to one of these families?
|
|
66
|
+
*
|
|
67
|
+
* The comparison folds CASE: every family name is written in lower case, and
|
|
68
|
+
* on a case-insensitive filesystem (Windows, and macOS by default) `SRC/x.ts`
|
|
69
|
+
* IS the file `src/x.ts`, so comparing the case exactly lets the spelling
|
|
70
|
+
* decide the verdict. BOTH lists are folded the same way, because both are
|
|
71
|
+
* judged against the same path: a case variant of an allow-listed file has to
|
|
72
|
+
* reach the same verdict as the file itself, or the fold would only move the
|
|
73
|
+
* inconsistency from one list to the other.
|
|
74
|
+
*
|
|
75
|
+
* THE TRADE-OFF, written down instead of left to look like an oversight: on a
|
|
76
|
+
* case-SENSITIVE filesystem a repository holding BOTH `src/` and `SRC/`
|
|
77
|
+
* refuses the edit under `SRC/` as well. That refusal is accepted on purpose.
|
|
78
|
+
* A wrongly allowed edit is a hole in the gate; a wrongly refused one is an
|
|
79
|
+
* inconvenience the caller can undo. Only the COMPARISON folds case - the
|
|
80
|
+
* path the tool asked for is echoed to the caller exactly as it was spelled,
|
|
81
|
+
* and the family a verdict names is the canonical one, not the folded form.
|
|
82
|
+
*/
|
|
64
83
|
function matchesAny(path, families) {
|
|
84
|
+
const folded = path.toLowerCase();
|
|
65
85
|
for (const fam of families) {
|
|
66
|
-
if (
|
|
86
|
+
if (folded.startsWith(fam.toLowerCase()))
|
|
67
87
|
return fam;
|
|
68
88
|
// also handle ".md" suffix pattern
|
|
69
|
-
if (fam.startsWith('.') &&
|
|
89
|
+
if (fam.startsWith('.') && folded.endsWith(fam.toLowerCase()))
|
|
70
90
|
return fam;
|
|
71
91
|
}
|
|
72
92
|
return null;
|
|
@@ -78,6 +98,43 @@ function stripLeadingDotSegments(path) {
|
|
|
78
98
|
out = out.slice(2);
|
|
79
99
|
return out;
|
|
80
100
|
}
|
|
101
|
+
/**
|
|
102
|
+
* Collapse the `.` and `..` segments of a RELATIVE path, lexically.
|
|
103
|
+
*
|
|
104
|
+
* The base directory does not enter the answer for a path that stays inside
|
|
105
|
+
* it: a `..` cancels the segment before it, for every base. A `..` that would
|
|
106
|
+
* leave the base is KEPT, so the result still reads as "outside", and a path
|
|
107
|
+
* outside the project belongs to no family.
|
|
108
|
+
*/
|
|
109
|
+
function collapseRelativeDotSegments(path) {
|
|
110
|
+
const out = [];
|
|
111
|
+
for (const segment of path.split('/')) {
|
|
112
|
+
if (segment === '' || segment === '.')
|
|
113
|
+
continue;
|
|
114
|
+
if (segment === '..') {
|
|
115
|
+
const last = out.length > 0 ? out[out.length - 1] : null;
|
|
116
|
+
if (last !== null && last !== '..')
|
|
117
|
+
out.pop();
|
|
118
|
+
else
|
|
119
|
+
out.push('..');
|
|
120
|
+
continue;
|
|
121
|
+
}
|
|
122
|
+
out.push(segment);
|
|
123
|
+
}
|
|
124
|
+
return out.join('/');
|
|
125
|
+
}
|
|
126
|
+
/**
|
|
127
|
+
* The path of `target` relative to `root`, when `target` is INSIDE `root`;
|
|
128
|
+
* `null` when it is not — the target is outside the root, or it is the root.
|
|
129
|
+
*/
|
|
130
|
+
function relativizeInsideRoot(target, root) {
|
|
131
|
+
const relativePath = normalizePath(relative(root, target));
|
|
132
|
+
if (relativePath.length === 0)
|
|
133
|
+
return null;
|
|
134
|
+
if (relativePath.startsWith('..') || isAbsolute(relativePath))
|
|
135
|
+
return null;
|
|
136
|
+
return stripLeadingDotSegments(relativePath);
|
|
137
|
+
}
|
|
81
138
|
/**
|
|
82
139
|
* The ONE spelling-independent form of a target path.
|
|
83
140
|
*
|
|
@@ -89,6 +146,7 @@ function stripLeadingDotSegments(path) {
|
|
|
89
146
|
*
|
|
90
147
|
* - separators fold to `/` (a Windows payload spells `src\x.ts`)
|
|
91
148
|
* - a leading `./` is dropped
|
|
149
|
+
* - a `..` segment is resolved
|
|
92
150
|
* - an ABSOLUTE path inside `projectRoot` becomes project-relative
|
|
93
151
|
* - an absolute path OUTSIDE `projectRoot` stays absolute: the families name
|
|
94
152
|
* THIS project's directories, and a path in another repository is another
|
|
@@ -97,23 +155,34 @@ function stripLeadingDotSegments(path) {
|
|
|
97
155
|
* - with no `projectRoot` an absolute path cannot be made relative and is
|
|
98
156
|
* left as it is
|
|
99
157
|
*
|
|
100
|
-
*
|
|
101
|
-
*
|
|
102
|
-
*
|
|
158
|
+
* The base a `..` is resolved against is the PROJECT ROOT the caller named,
|
|
159
|
+
* and that is a fact about the caller rather than a guess: the IDE invokes
|
|
160
|
+
* `peaks code-gate --project "<the project directory>"`, and the tool call's
|
|
161
|
+
* own working directory is that same project directory. A `..` that resolves
|
|
162
|
+
* OUTSIDE the root names a file outside the project, so it belongs to no
|
|
163
|
+
* family and is allowed - the same rule an absolute path outside the root
|
|
164
|
+
* follows. The trade-off is written down rather than left implicit: a base
|
|
165
|
+
* chosen wrongly would refuse files of a neighbouring directory, and the
|
|
166
|
+
* project root is the one base both the caller and the tool call agree on.
|
|
103
167
|
*/
|
|
104
168
|
export function normalizeGatePath(filePath, projectRoot) {
|
|
105
169
|
if (filePath.length === 0)
|
|
106
170
|
return '';
|
|
107
171
|
const slashed = normalizePath(filePath);
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
return stripLeadingDotSegments(relativePath);
|
|
114
|
-
}
|
|
172
|
+
const root = typeof projectRoot === 'string' && projectRoot.length > 0 ? resolve(projectRoot) : null;
|
|
173
|
+
if (isAbsolute(slashed)) {
|
|
174
|
+
if (root === null)
|
|
175
|
+
return slashed;
|
|
176
|
+
return relativizeInsideRoot(resolve(slashed), root) ?? slashed;
|
|
115
177
|
}
|
|
116
|
-
|
|
178
|
+
if (root === null)
|
|
179
|
+
return collapseRelativeDotSegments(stripLeadingDotSegments(slashed));
|
|
180
|
+
const resolved = resolve(root, slashed);
|
|
181
|
+
const inside = relativizeInsideRoot(resolved, root);
|
|
182
|
+
if (inside !== null)
|
|
183
|
+
return inside;
|
|
184
|
+
// The `..` left the project root: the target is another project's file.
|
|
185
|
+
return normalizePath(resolved);
|
|
117
186
|
}
|
|
118
187
|
/**
|
|
119
188
|
* Pure decision function. Given the tool name + input object, return
|
|
@@ -127,7 +196,11 @@ export function normalizeGatePath(filePath, projectRoot) {
|
|
|
127
196
|
*
|
|
128
197
|
* `projectRoot` is the root the deny families are relative to. It is what
|
|
129
198
|
* lets an ABSOLUTE path be judged like its relative spelling; without it an
|
|
130
|
-
* absolute path cannot be related to the project and is left alone.
|
|
199
|
+
* absolute path cannot be related to the project and is left alone. It is the
|
|
200
|
+
* project root the CALLER named, not the canonical root above it: a project
|
|
201
|
+
* nested inside a git repository is judged against itself, and the canonical
|
|
202
|
+
* root - where the session and the leases live - is a different question
|
|
203
|
+
* that this parameter does not answer.
|
|
131
204
|
*/
|
|
132
205
|
export function decideGateAction(tool, input, driver, projectRoot) {
|
|
133
206
|
// Only gate Edit / Write / MultiEdit.
|
|
@@ -151,7 +224,8 @@ export function decideGateAction(tool, input, driver, projectRoot) {
|
|
|
151
224
|
if (allowMatch !== null) {
|
|
152
225
|
return { action: 'allow' };
|
|
153
226
|
}
|
|
154
|
-
// Hard-blocked family check
|
|
227
|
+
// Hard-blocked family check — case-insensitively, because every family name
|
|
228
|
+
// is lower-case and the filesystem holding the file may not be.
|
|
155
229
|
const denyMatch = matchesAny(filePath, HARD_BLOCKED_PATH_FAMILIES);
|
|
156
230
|
if (denyMatch !== null) {
|
|
157
231
|
// A driver that is not the fast lane falls through to the same deny a
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "peaks-loop",
|
|
3
|
-
"version": "4.1.
|
|
3
|
+
"version": "4.1.15",
|
|
4
4
|
"description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
|
|
5
5
|
"author": "SquabbyZ",
|
|
6
6
|
"keywords": [
|
|
@@ -129,10 +129,10 @@
|
|
|
129
129
|
"picomatch": "4.0.7",
|
|
130
130
|
"yaml": "^2.9.1",
|
|
131
131
|
"zod": "^4.6.7",
|
|
132
|
-
"peaks-loop-mut": "0.1.
|
|
133
|
-
"peaks-loop-shared
|
|
134
|
-
"peaks-loop-
|
|
135
|
-
"peaks-loop-
|
|
132
|
+
"peaks-loop-mut": "0.1.69",
|
|
133
|
+
"peaks-loop-shared": "0.0.104",
|
|
134
|
+
"peaks-loop-internal-runtime": "0.0.55",
|
|
135
|
+
"peaks-loop-shared-channel": "0.0.72"
|
|
136
136
|
},
|
|
137
137
|
"devDependencies": {
|
|
138
138
|
"@changesets/cli": "2.31.1",
|