dsh-perm-gate 3.0.0 → 4.1.0-beta.1

package/INSTALL.ja.md

@@ -12,7 +12,7 @@
 - [日本語 changelog](./CHANGELOG.ja.md)
 - [한국어 changelog](./CHANGELOG.ko.md)
 
-`dsh-perm-gate` バージョン **2.6.0**。判定チェーン、ルールファイル形式、自动审查
+`dsh-perm-gate` バージョン **2.4.1**。判定チェーン、ルールファイル形式、自动审查
 ティアについては [日本語 README](./README.ja.md) を参照してください。
 
 ## 必要条件
@@ -23,20 +23,19 @@
 - インストール先の profile。ブラウザ側は `web` profile 向けにのみビルドされます
   （`package.json` の `dsh.client.platform = "web"`）。
 
-## DSH のバージョンに合うラインを選ぶ
+## DSH のバージョンに合う tag を選ぶ
 
-2 つの長期ブランチが 2 つの DSH ラインを担当します：`main`（2.x）と
-`sync/0.1.5-from-main`（3.x、DSH 0.1.5 のパッケージング変体 —— `compat/0.1.5` は
-同じコードツリーを指します）。
+単一ビルドが DSH 両ラインをカバーするため、どちらの tag を選んでも動作するコードが
+インストールされます —— tag を残しておくのは、あなたがピン留めするバージョンが
+各ラインで意味を持つようにするためです。
 
 | DSH のバージョン | インストール方法 |
 |-----------------|-----------------|
-| `0.1.2-alpha.1` – `0.1.5-rc.0` | `dsh plugin --profile web add dsh-perm-gate`（tag `latest`、2.x ライン） |
-| `0.1.5-rc.1` 以上 | `dsh plugin --profile web add github:drscrewdriver/dsh-perm-gate#sync/0.1.5-from-main`（3.x ライン；npm の dist-tag は未公開 —— `@latest` は同じコードの 2.x パッケージングをインストールします） |
+| `0.1.2-alpha.1` 以上（`0.1.5-rc.2` を含む） | `dsh plugin --profile web add dsh-perm-gate`（tag `latest`） |
 | `0.1.1-rc.2` まで | `dsh plugin --profile web add dsh-perm-gate@legacy` |
 
-DSH は `engines.dsh` を強制しないため、tag と ref は選択メカニズムであり、互換性
-ゲートそのものではありません。ラインと tag の公開レイアウトについては
+DSH は `engines.dsh` を強制しないため、tag が選択メカニズムであり、互換性ゲート
+そのものではありません。単一ビルドが両ラインをカバーする理由と tag の公開方法については、
 [RELEASING.md](./RELEASING.md) を参照してください。
 
 ## 公式 CLI でインストール
@@ -73,11 +72,6 @@ profile の `cordis.yml` にプラグインを追加します：
     defaultAction: ask              # allow | ask | deny
 ```
 
-2.6.0 から、ルール本体は `dsh-perm-gate-rules` settings 名前空間に保存され、変更の
-たびにゲートがその場で再コンパイルされます。上記の YAML ファイルは任意になりました。
-名前空間が未設定の間だけ読み込まれ、プラグインが最初にルールを書き込む際（許可リスト
-の承認、または設定 UI での編集）にファイルのルールが自動的に取り込まれます。
-
 まずは [examples/permissions.example.yaml](./examples/permissions.example.yaml)
 から始め、profile を再読込してください。
 

package/INSTALL.ko.md

@@ -12,7 +12,7 @@
 - [日本語 changelog](./CHANGELOG.ja.md)
 - [한국어 changelog](./CHANGELOG.ko.md)
 
-`dsh-perm-gate` 버전 **2.6.0**. 결정 체인, 규칙 파일 형식, 自动审查 티어는
+`dsh-perm-gate` 버전 **2.4.1**. 결정 체인, 규칙 파일 형식, 自动审查 티어는
 [한국어 README](./README.ko.md)를 참고하세요.
 
 ## 요구 사항
@@ -23,21 +23,20 @@
 - 설치할 profile. 브라우저 절반은 `web` profile용으로만 빌드됩니다
   (`package.json`의 `dsh.client.platform = "web"`).
 
-## DSH 버전에 맞는 라인 선택
+## DSH 버전에 맞는 tag 선택
 
-두 개의 장기 브랜치가 두 DSH 라인을 담당합니다: `main`(2.x)과
-`sync/0.1.5-from-main`(3.x, DSH 0.1.5 패키징 변형 —— `compat/0.1.5`는 같은 코드
-트리를 가리킵니다).
+단일 빌드는 두 DSH 라인을 모두 커버하므로, 어느 tag를 골라도 작동하는 코드가
+설치됩니다 —— tag를 유지하는 이유는 당신이 고정하는 버전이 각 라인에서 의미 있게
+유지되도록 하기 위함입니다.
 
 | DSH 버전 | 설치 방법 |
 |----------|-----------|
-| `0.1.2-alpha.1` – `0.1.5-rc.0` | `dsh plugin --profile web add dsh-perm-gate` (tag `latest`, 2.x 라인) |
-| `0.1.5-rc.1` 이상 | `dsh plugin --profile web add github:drscrewdriver/dsh-perm-gate#sync/0.1.5-from-main` (3.x 라인; npm dist-tag 미게시 —— `@latest`는 동일 코드의 2.x 패키징을 설치) |
+| `0.1.2-alpha.1` 이상 (`0.1.5-rc.2` 포함) | `dsh plugin --profile web add dsh-perm-gate` (tag `latest`) |
 | `0.1.1-rc.2` 이하 | `dsh plugin --profile web add dsh-perm-gate@legacy` |
 
-DSH는 `engines.dsh`를 강제하지 않으므로, tag과 ref은 선택 메커니즘이지 호환성
-게이트가 아닙니다. 라인과 tag 게시 레이아웃은 [RELEASING.md](./RELEASING.md)를
-참고하세요.
+DSH는 `engines.dsh`를 강제하지 않으므로, tag는 선택 메커니즘이지 호환성 게이트가
+아닙니다. 단일 아티팩트가 두 라인을 커버하는 이유와 tag가 게시되는 방식에 대해서는
+[RELEASING.md](./RELEASING.md)를 참고하세요.
 
 ## 공식 CLI로 설치
 
@@ -74,11 +73,6 @@ profile의 `cordis.yml`에 플러그인을 추가합니다:
     defaultAction: ask              # allow | ask | deny
 ```
 
-2.6.0부터 규칙 본체는 `dsh-perm-gate-rules` settings 네임스페이스에 저장되며, 변경 시
-마다 게이트가 그 자리에서 다시 컴파일됩니다. 위의 YAML 파일은 선택 사항이 되었습니다.
-네임스페이스가 설정되지 않은 동안에만 읽히며, 플러그인이 처음으로 규칙을 쓸 때(허용
-목록 승인 또는 설정 UI에서의 편집) 파일의 규칙이 자동으로 흡수됩니다.
-
 [examples/permissions.example.yaml](./examples/permissions.example.yaml)에서 시작한 뒤
 profile을 다시 불러오세요.
 

package/INSTALL.md

@@ -12,7 +12,7 @@
 - [日本語 changelog](./CHANGELOG.ja.md)
 - [한국어 changelog](./CHANGELOG.ko.md)
 
-`dsh-perm-gate` version **2.6.0**. Continue with the [README](./README.md) for the
+`dsh-perm-gate` version **2.4.1**. Continue with the [README](./README.md) for the
 decision chain, the rules file format and the 自动审查 tier.
 
 ## Requirements
@@ -23,21 +23,19 @@ decision chain, the rules file format and the 自动审查 tier.
 - A profile to install into — the browser half only ships for the `web` profile
   (`dsh.client.platform = "web"` in `package.json`).
 
-## Pick the line for your DSH version
+## Pick the tag for your DSH version
 
-Two long-lived branches serve two DSH lines: `main` (2.x) and
-`sync/0.1.5-from-main` (3.x, the DSH 0.1.5 packaging variant — `compat/0.1.5`
-points at the same tree).
+One build serves both DSH lines, so either tag installs working code — the tag
+exists so a version you pin stays meaningful per line.
 
 | Your DSH | Install |
 |----------|---------|
-| `0.1.2-alpha.1` – `0.1.5-rc.0` | `dsh plugin --profile web add dsh-perm-gate` (tag `latest`, the 2.x line) |
-| `0.1.5-rc.1` or newer | `dsh plugin --profile web add github:drscrewdriver/dsh-perm-gate#sync/0.1.5-from-main` (the 3.x line; no npm dist-tag yet — `@latest` installs the same code with 2.x packaging) |
+| `0.1.2-alpha.1` or newer (incl. `0.1.5-rc.2`) | `dsh plugin --profile web add dsh-perm-gate` (tag `latest`) |
 | up to `0.1.1-rc.2` | `dsh plugin --profile web add dsh-perm-gate@legacy` |
 
-DSH does not enforce `engines.dsh`, so tags and refs are the selection mechanism
-rather than a compatibility gate. See [RELEASING.md](./RELEASING.md) for how the
-lines and tags are laid out.
+DSH does not enforce `engines.dsh`, so the tags are the selection mechanism rather
+than a compatibility gate. See [RELEASING.md](./RELEASING.md) for why one artifact
+covers both lines and how the tags are published.
 
 ## Install with the official CLI
 
@@ -75,12 +73,6 @@ Add the plugin to your profile's `cordis.yml`:
     gatePresets: [permissive]       # tiers where the gate is active at all (default)
 ```
 
-Since 2.6.0 the rules themselves are stored in the `dsh-perm-gate-rules` settings
-namespace, and every change recompiles the gate in place. The YAML file above is
-optional: it is only read while the namespace is untouched, and the first rules
-write from the plugin (an allowlist approval, or an edit in the settings UI)
-absorbs the file's rules automatically.
-
 Start from [examples/permissions.example.yaml](./examples/permissions.example.yaml),
 then reload the profile.
 

package/INSTALL.zh.md

@@ -12,7 +12,7 @@
 - [日本語 changelog](./CHANGELOG.ja.md)
 - [한국어 changelog](./CHANGELOG.ko.md)
 
-`dsh-perm-gate` 版本 **2.6.0**。裁决链、规则文件格式与自动审查档位请见
+`dsh-perm-gate` 版本 **2.4.1**。裁决链、规则文件格式与自动审查档位请见
 [中文 README](./README.zh.md)。
 
 ## 前置条件
@@ -23,19 +23,18 @@
 - 需要一个目标 profile —— 浏览器端只为 `web` profile 构建（`package.json`
   里 `dsh.client.platform = "web"`）。
 
-## 按你的 DSH 版本选择安装线
+## 按你的 DSH 版本选择 tag
 
-两条长期分支分别服务两条 DSH 线：`main`（2.x）与 `sync/0.1.5-from-main`
-（3.x，DSH 0.1.5 打包变体 —— `compat/0.1.5` 指向同一棵代码树）。
+单一构建同时覆盖两条 DSH 线，所以任一 tag 安装的代码都能工作 —— 保留 tag
+是为了让你锁定的版本在每条线上都有意义。
 
 | 你的 DSH | 安装方式 |
 |----------|----------|
-| `0.1.2-alpha.1` – `0.1.5-rc.0` | `dsh plugin --profile web add dsh-perm-gate`（tag `latest`，2.x 线） |
-| `0.1.5-rc.1` 或更高 | `dsh plugin --profile web add github:drscrewdriver/dsh-perm-gate#sync/0.1.5-from-main`（3.x 线；npm 尚无对应 dist-tag —— `@latest` 安装的是相同代码的 2.x 打包） |
+| `0.1.2-alpha.1` 或更高（含 `0.1.5-rc.2`） | `dsh plugin --profile web add dsh-perm-gate`（tag `latest`） |
 | 不高于 `0.1.1-rc.2` | `dsh plugin --profile web add dsh-perm-gate@legacy` |
 
-DSH 不强制 `engines.dsh`，因此 tag 与 ref 是选择机制而非兼容性关卡。
-各线与 tag 的发布布局详见 [RELEASING.md](./RELEASING.md)。
+DSH 不强制 `engines.dsh`，因此 tag 是选择机制而非兼容性关卡。
+详见 [RELEASING.md](./RELEASING.md) 了解为何单一制品覆盖两条线以及 tag 的发布方式。
 
 ## 用官方 CLI 安装
 
@@ -71,10 +70,6 @@ dsh plugin --profile web add .
     defaultAction: ask              # allow | ask | deny
 ```
 
-自 2.6.0 起，规则本体存储在 `dsh-perm-gate-rules` settings 命名空间中，每次变更都会
-就地重编译闸门。上面的 YAML 文件变为可选：只有命名空间未被配置时才会读取它，插件
-发起的首次规则写入（白名单批准或设置界面编辑）会自动收编文件中的规则。
-
 可从 [examples/permissions.example.yaml](./examples/permissions.example.yaml) 起步，
 然后重载 profile。
 

package/README.ja.md

@@ -27,8 +27,7 @@
 > | DSH バージョン | ブランチ | バージョン | npm タグ |
 > | --- | --- | --- | --- |
 > | 0.1.0-rc.7 ~ 0.1.1-rc.x | `legacy` | `1.x` | `@legacy` |
-> | 0.1.2-alpha.1 ~ 0.1.5-rc.0 | `main` | `2.x` | `@latest` / `@dsh-0.1.2` （`@2.x` は範囲） |
-> | 0.1.5-rc.1+ | `sync/0.1.5-from-main`（=`compat/0.1.5`） | `3.x` | GitHub ref インストール（dist-tag 未公開） |
+> | 0.1.2-alpha.1+（0.1.5-rc.2を含む） | `main` | `2.x` | `@latest` / `@dsh-0.1.2` （`@2.x` は範囲） |
 >
 > バージョン系列は **DSH ライン**を追います（`1.x` = DSH ≤ 0.1.1、`2.x` = DSH 0.1.2+）。
 > メジャー同士が互いを遮断するため、`^1.x` のインストールが `2.x` を解決することは
@@ -46,7 +45,7 @@
 > メソッドであるため、`typeof` プロブで読み取り、欠落時やエラー時には「ポリシー
 > 不明」にフォールバックします。
 
-バージョン **2.6.0** — 変更履歴は [日本語 changelog](./CHANGELOG.ja.md) を参照。
+バージョン **2.4.1** — 変更履歴は [日本語 changelog](./CHANGELOG.ja.md) を参照。
 
 DeepSeek Harness 向けの、単一・自己完結・決定論優先・fail-closed な権限ゲートです。
 

package/README.ko.md

@@ -27,8 +27,7 @@
 > | DSH 버전 | 브랜치 | 버전 | npm 태그 |
 > | --- | --- | --- | --- |
 > | 0.1.0-rc.7 ~ 0.1.1-rc.x | `legacy` | `1.x` | `@legacy` |
-> | 0.1.2-alpha.1 ~ 0.1.5-rc.0 | `main` | `2.x` | `@latest` / `@dsh-0.1.2` (`@2.x`는 범위) |
-> | 0.1.5-rc.1+ | `sync/0.1.5-from-main` (=`compat/0.1.5`) | `3.x` | GitHub ref 설치 (dist-tag 미게시) |
+> | 0.1.2-alpha.1+ (0.1.5-rc.2 포함) | `main` | `2.x` | `@latest` / `@dsh-0.1.2` (`@2.x`는 범위) |
 >
 > 버전 계열은 **DSH 라인**을 따릅니다(`1.x` = DSH ≤ 0.1.1, `2.x` = DSH 0.1.2+). 메이저
 > 버전이 서로를 차단하므로 `^1.x` 설치가 `2.x`를 해석하는 일은 없고 그 반대도
@@ -44,7 +43,7 @@
 > 모두에서 user-approval 서비스의 **개인** 메소드이므로 `typeof` 프로브를 통해
 > 읽으며, 누락되거나 예외 발생 시 "정책_unknown"으로 후퇴합니다.
 
-버전 **2.6.0** — 변경 내역은 [한국어 changelog](./CHANGELOG.ko.md)를 참고하세요.
+버전 **2.4.1** — 변경 내역은 [한국어 changelog](./CHANGELOG.ko.md)를 참고하세요.
 
 DeepSeek Harness용 단일·자족적·결정론 우선·fail-closed 권한 게이트입니다.
 

package/README.md

@@ -26,8 +26,7 @@
 > | DSH version | Branch | Version | npm tag |
 > | --- | --- | --- | --- |
 > | 0.1.0-rc.7 ~ 0.1.1-rc.x | `legacy` | `1.x` | `@legacy` |
-> | 0.1.2-alpha.1 ~ 0.1.5-rc.0 | `main` | `2.x` | `@latest` / `@dsh-0.1.2` (`@2.x` is a range) |
-> | 0.1.5-rc.1+ | `sync/0.1.5-from-main` (=`compat/0.1.5`) | `3.x` | GitHub ref install (no dist-tag yet) |
+> | 0.1.2-alpha.1+ (incl. 0.1.5-rc.2) | `main` | `2.x` | `@latest` / `@dsh-0.1.2` (`@2.x` is a range) |
 >
 > The series number tracks the **DSH line** (`1.x` = DSH ≤ 0.1.1, `2.x` = DSH 0.1.2+),
 > and the majors fence each other: a `^1.x` install never resolves a `2.x` release and

package/README.zh.md

@@ -25,8 +25,7 @@
 > | DSH 版本 | 分支 | 版本号 | npm 标签 |
 > | --- | --- | --- | --- |
 > | 0.1.0-rc.7 ~ 0.1.1-rc.x | `legacy` | `1.x` | `@legacy` |
-> | 0.1.2-alpha.1 ~ 0.1.5-rc.0 | `main` | `2.x` | `@latest` / `@dsh-0.1.2` （`@2.x` 是范围） |
-> | 0.1.5-rc.1+ | `sync/0.1.5-from-main`（=`compat/0.1.5`） | `3.x` | GitHub ref 安装（暂无 dist-tag） |
+> | 0.1.2-alpha.1+（含 0.1.5-rc.2） | `main` | `2.x` | `@latest` / `@dsh-0.1.2` （`@2.x` 是范围） |
 >
 > 版本序列号跟的是 **DSH 线**（`1.x` = DSH ≤ 0.1.1，`2.x` = DSH 0.1.2+），两条大版本互
 > 相隔离：锁在 `^1.x` 的安装绝不会解析到 `2.x`，反之亦然。`engines.dsh` 表达同样的
@@ -40,7 +39,7 @@
 > 线上都是 user-approval 服务的**私有**方法，因此通过 `typeof` 探测读取，缺失
 > 或抛错时降级为「策略未知」。
 
-版本 **2.6.0** —— 变更见 [Changelog](./CHANGELOG.md)。
+版本 **2.4.1** —— 变更见 [Changelog](./CHANGELOG.md)。
 
 一个**单一自足、确定性优先、fail-closed** 的 DeepSeek Harness 权限门插件。
 

package/lib/client.js

@@ -405,7 +405,6 @@ window.__ModuleLoader__.load({
 		* learning.json store the gate reads); actions POST back. Best-effort: a
 		* missing route renders the empty state, never an error.
 		*/
-		const POLL_MS$2 = 5e3;
 		const itemStyle = {
 			display: "flex",
 			alignItems: "center",
@@ -435,6 +434,8 @@ window.__ModuleLoader__.load({
 		};
 		function SedimentSection({ t }) {
 			const [body, setBody] = (0, react.useState)(null);
+			/** Latest loader, so a mutation can refresh the list without owning the fetch. */
+			const reloadRef = (0, react.useRef)(() => {});
 			(0, react.useEffect)(() => {
 				let alive = true;
 				const load = () => {
@@ -444,11 +445,18 @@ window.__ModuleLoader__.load({
 						if (alive) setBody({});
 					});
 				};
+				reloadRef.current = load;
 				load();
-				const timer = setInterval(load, POLL_MS$2);
+				const onVisible = () => {
+					if (document.visibilityState === "visible") load();
+				};
+				window.addEventListener("focus", onVisible);
+				document.addEventListener("visibilitychange", onVisible);
 				return () => {
 					alive = false;
-					clearInterval(timer);
+					reloadRef.current = () => {};
+					window.removeEventListener("focus", onVisible);
+					document.removeEventListener("visibilitychange", onVisible);
 				};
 			}, []);
 			const post = (payload) => {
@@ -456,6 +464,8 @@ window.__ModuleLoader__.load({
 					method: "POST",
 					headers: { "content-type": "application/json" },
 					body: JSON.stringify(payload)
+				}).then(() => {
+					reloadRef.current();
 				}).catch(() => {});
 			};
 			const threshold = body?.threshold ?? 3;
@@ -2009,6 +2019,95 @@ window.__ModuleLoader__.load({
 			const body = await res.json();
 			return Array.isArray(body.events) ? body.events : [];
 		}
+		/** The host's push route (see src/events.ts); the browser half prefers it to polling. */
+		const STREAM_ROUTE = "/api/dsh-perm-gate/stream";
+		/** Stream attempts before the route is written off as unsupported and polling takes over. */
+		const STREAM_RETRIES = 3;
+		const STREAM_RETRY_MS = 3e3;
+		/**
+		* Degraded path only: a host predating the stream route still gets a servable
+		* strip. Deliberately slower than the old 2 s tick — it now also pauses while
+		* the tab is hidden, so a backgrounded page costs nothing.
+		*/
+		const FALLBACK_POLL_MS = 5e3;
+		/**
+		* Follow one session's decision feed until the returned close is called.
+		*
+		* Prefers the host's `text/event-stream` route, which pushes each decision as
+		* the gate appends it — no timer, no repeated re-read of the event log. When
+		* the stream is unavailable (an older host, a proxy that buffers it) this
+		* degrades to polling the JSON route, gated on page visibility.
+		*
+		* @param sessionId - the session whose decisions to follow.
+		* @param getSince - cursor supplier, read at connect and on every fallback poll.
+		* @param onBatch - receives the backlog, then live batches.
+		* @returns the close: ends the stream and any fallback timer.
+		*/
+		function followEvents(sessionId, getSince, onBatch) {
+			let closed = false;
+			let source = null;
+			let pollTimer = null;
+			let retries = 0;
+			let polls = 0;
+			const stopPolling = () => {
+				if (pollTimer === null) return;
+				clearInterval(pollTimer);
+				pollTimer = null;
+			};
+			const poll = () => {
+				if (closed) return;
+				if (typeof document !== "undefined" && document.visibilityState === "hidden") return;
+				const backlog = polls === 0;
+				polls += 1;
+				fetchEvents(sessionId, getSince()).then((events) => {
+					if (!closed) onBatch({
+						events,
+						backlog
+					});
+				}).catch(() => {});
+			};
+			const startPolling = () => {
+				if (closed || pollTimer !== null) return;
+				polls = 0;
+				poll();
+				pollTimer = setInterval(poll, FALLBACK_POLL_MS);
+			};
+			const connect = () => {
+				if (closed) return;
+				const query = `?sessionId=${encodeURIComponent(sessionId)}&since=${getSince()}`;
+				const next = new EventSource(`${STREAM_ROUTE}${query}`);
+				source = next;
+				next.onopen = () => {
+					retries = 0;
+					stopPolling();
+				};
+				next.onmessage = (message) => {
+					try {
+						const body = JSON.parse(message.data);
+						if (Array.isArray(body.events)) onBatch({
+							events: body.events,
+							backlog: body.backlog === true
+						});
+					} catch {}
+				};
+				next.onerror = () => {
+					if (source === next) source = null;
+					next.close();
+					if (closed) return;
+					retries += 1;
+					startPolling();
+					if (retries <= STREAM_RETRIES) setTimeout(connect, STREAM_RETRY_MS);
+				};
+			};
+			if (typeof EventSource === "undefined") startPolling();
+			else connect();
+			return () => {
+				closed = true;
+				source?.close();
+				source = null;
+				stopPolling();
+			};
+		}
 		/** Resolve the current session id from slot props (top level, nested, or hook). */
 		function resolveSessionId(props) {
 			const direct = props?.sessionId;
@@ -2195,15 +2294,15 @@ window.__ModuleLoader__.load({
 		* dsh-perm-gate (a simplified version of the review-feed pattern demonstrated
 		* by dsh-approval-gate).
 		*
-		* Polls the host's `GET /api/dsh-perm-gate/events?sessionId=&since=` feed every
-		* 2 s and shows the latest decision above the conversation input: auto-allows
-		* (green) and denies (red) auto-dismiss after a few seconds; an ask (amber)
-		* stays until the next event because it needs the human's attention.
+		* Follows the host's decision feed (`GET /api/dsh-perm-gate/stream`, an SSE
+		* push; see `followEvents` for the older-host polling fallback) and shows the
+		* latest decision above the conversation input: auto-allows (green) and denies
+		* (red) auto-dismiss after a few seconds; an ask (amber) stays until the next
+		* event because it needs the human's attention.
 		*
 		* Everything is best-effort: no session id, a missing route, or any fetch
 		* failure simply means "render nothing". No @deepseek-ai value imports.
 		*/
-		const POLL_MS$1 = 2e3;
 		const AUTO_HIDE_MS = 4e3;
 		/** Localized tag for a manual terminal state; other kinds keep their short tag. */
 		function manualTagKey(kind) {
@@ -2224,35 +2323,27 @@ window.__ModuleLoader__.load({
 				setNotice(null);
 				if (sessionId === null) return;
 				let alive = true;
-				let timer = null;
-				const startPolling = () => {
-					if (!alive) return;
-					timer = setInterval(() => {
-						fetchEvents(sessionId, sinceRef.current).then((events) => {
-							if (!alive || events.length === 0) return;
-							const last = events[events.length - 1];
-							if (last === void 0 || last.id <= shownIdRef.current) return;
-							shownIdRef.current = last.id;
-							sinceRef.current = last.id;
-							setNotice(last);
-							if (hideTimerRef.current !== null) clearTimeout(hideTimerRef.current);
-							if (!presentation(last.kind).sticky) hideTimerRef.current = setTimeout(() => {
-								setNotice(null);
-							}, AUTO_HIDE_MS);
-						}).catch(() => {});
-					}, POLL_MS$1);
-				};
-				fetchEvents(sessionId, 0).then((events) => {
-					if (!alive) return;
-					if (events.length > 0) {
-						sinceRef.current = events[events.length - 1]?.id ?? 0;
+				const onBatch = (batch) => {
+					if (!alive || batch.events.length === 0) return;
+					const last = batch.events[batch.events.length - 1];
+					if (last === void 0) return;
+					if (last.id > sinceRef.current) sinceRef.current = last.id;
+					if (batch.backlog) {
 						shownIdRef.current = sinceRef.current;
+						return;
 					}
-					startPolling();
-				}).catch(startPolling);
+					if (last.id <= shownIdRef.current) return;
+					shownIdRef.current = last.id;
+					setNotice(last);
+					if (hideTimerRef.current !== null) clearTimeout(hideTimerRef.current);
+					if (!presentation(last.kind).sticky) hideTimerRef.current = setTimeout(() => {
+						setNotice(null);
+					}, AUTO_HIDE_MS);
+				};
+				const close = followEvents(sessionId, () => sinceRef.current, onBatch);
 				return () => {
 					alive = false;
-					if (timer !== null) clearInterval(timer);
+					close();
 					if (hideTimerRef.current !== null) clearTimeout(hideTimerRef.current);
 				};
 			}, [sessionId]);
@@ -2335,7 +2426,8 @@ window.__ModuleLoader__.load({
 		* Approval-history view — the `conversation.view` face of dsh-perm-gate,
 		* following the session-scoped review-page pattern demonstrated by
 		* dsh-approval-gate: a timeline of every gate decision in the current
-		* conversation, newest first, refreshed by polling.
+		* conversation, newest first, loaded once and then extended by the host's push
+		* feed (see `followEvents`).
 		*
 		* Beyond the decision timeline this view owns the review data plane: a snapshot
 		* inventory bar (with session/all clearing), per-event file chips, and a diff
@@ -2347,7 +2439,6 @@ window.__ModuleLoader__.load({
 		* routes. Everything is best-effort: no session id or any fetch failure renders
 		* the empty / error state. No @deepseek-ai value imports.
 		*/
-		const POLL_MS = 5e3;
 		/** Tag text per event kind, keyed into the plugin dictionary. */
 		const TAG_KEYS = {
 			auto: "history.tag.auto",
@@ -2761,29 +2852,47 @@ window.__ModuleLoader__.load({
 				setEvents(null);
 				setError(null);
 				setStats(null);
+				if (sessionId === null) {
+					setEvents([]);
+					return;
+				}
 				let alive = true;
-				const load = () => {
+				let cursor = 0;
+				let closeStream = null;
+				fetchSnapshotStats(sessionId).then((next) => {
+					if (alive) setStats(next);
+				});
+				/**
+				* Decisions landing after the initial load. Both the stream's pushes and the
+				* fallback's ticks carry only events past the cursor, so they merge the same
+				* way; a batch is also the point where the snapshot inventory can have grown.
+				*/
+				const onBatch = (batch) => {
+					if (!alive || batch.events.length === 0) return;
+					for (const ev of batch.events) if (ev.id > cursor) cursor = ev.id;
+					setEvents((current) => {
+						const known = new Set((current ?? []).map((ev) => ev.id));
+						const added = batch.events.filter((ev) => !known.has(ev.id));
+						return added.length === 0 ? current : [...added, ...current ?? []].sort((a, b) => b.id - a.id);
+					});
+					setError(null);
 					fetchSnapshotStats(sessionId).then((next) => {
 						if (alive) setStats(next);
 					});
-					if (sessionId === null) {
-						setEvents([]);
-						return;
-					}
-					fetchEvents(sessionId, 0).then((loaded) => {
-						if (!alive) return;
-						setEvents([...loaded].sort((a, b) => b.id - a.id));
-						setError(null);
-					}).catch((e) => {
-						if (!alive) return;
-						setError(String(e?.message ?? e));
-					});
 				};
-				load();
-				const timer = setInterval(load, POLL_MS);
+				fetchEvents(sessionId, 0).then((loaded) => {
+					if (!alive) return;
+					setEvents([...loaded].sort((a, b) => b.id - a.id));
+					setError(null);
+					cursor = loaded.reduce((max, ev) => ev.id > max ? ev.id : max, 0);
+				}).catch((e) => {
+					if (alive) setError(String(e?.message ?? e));
+				}).finally(() => {
+					if (alive) closeStream = followEvents(sessionId, () => cursor, onBatch);
+				});
 				return () => {
 					alive = false;
-					clearInterval(timer);
+					closeStream?.();
 				};
 			}, [sessionId]);
 			/** Whether one event has a snapshot covering this file (chip is clickable). */