integrate-peekling

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Integrate Peekling

集成Peekling

Require the host environment, runtime URL/version, pack URL/id, desired position, and CSP/deployment constraints.

Use the documented ESM API or the exact two-line declarative browser setup with canonical
```
Peekling.hatch(...)
```
. There is no public
```
run(...)
```
operation. Never invent a one-line install.
Define semantic mappings in the immutable Plan before hatch. Await readiness, keep the returned instance, admit bounded application facts with
```
emit(...)
```
, use bounded
```
override(...)
```
for validated exact-state control, and call
```
destroy()
```
on teardown.
Verify pack CORS/MIME, CSP, Shadow DOM isolation, no focus/event interference, reduced motion, responsive bounds, and one selected density request.
Test failure fallback and no-JS content. Do not add telemetry, backend requirements, or executable pack logic.

Use only capabilities actually available. If a required command/tool cannot run, provide the exact handoff and state that it remains unverified. The workflow is agent-neutral.

agents/openai.yaml

is optional metadata, not a dependency.

需要宿主环境、运行时URL/版本、包URL/ID、期望位置以及CSP/部署约束。

使用文档化的ESM API或标准的
```
Peekling.hatch(...)
```
实现精确的两行式声明式浏览器配置。不存在公开的
```
run(...)
```
操作，切勿自行编写一行式安装代码。
在调用hatch之前，在不可变的Plan中定义语义映射。等待就绪状态，保留返回的实例，使用
```
emit(...)
```
传递有限的应用程序信息，使用受限的
```
override(...)
```
实现经过验证的精确状态控制，并在销毁阶段调用
```
destroy()
```
。
验证包的CORS/MIME、CSP、Shadow DOM隔离性、无焦点/事件干扰、减少动画、响应式边界以及单一选定的密度请求。
测试故障回退和无JavaScript环境下的内容。请勿添加遥测、后端依赖或可执行的包逻辑。

仅使用实际可用的功能。如果所需命令/工具无法运行，请提供确切的交接信息并说明其状态未经验证。此工作流与Agent无关。

agents/openai.yaml

是可选元数据，而非依赖项。