zhuyuan-ice-gl-zy001/ZCODE-DEV-20260902/zcode-zc001-wxapp-devtools-fix-20260902/TCS-EVENT-ZY001-ZCODE-ZC001-WXAPP-DEVTOOLS-FIX-20260902.human.en-US.md

# Zhuyuan Wake and WeChat Mini-Program DevTools Error and Preview Fix Event · Human Engineering Language (English)

> This is an English reading projection of validated native TCS/HLDP source. It is not a new canonical source and grants no execution authority.

## What this is

This is a **event** declaration with identifier `TCS-EVENT-ZY001-ZCODE-ZC001-WXAPP-DEVTOOLS-FIX-20260902` and version `0.1.0`. The projector validates it with the Stage-1 compiler before changing its reading order.

## Who is here

- **subject**  `subject`
  - **channel_id**：ICE-CH-ZC001  `subject.channel_id`
  - **subject_id**：ICE-P-ZY001  `subject.subject_id`
  - **subject_kind**：PERSONA  `subject.subject_kind`
  - **verification**：zy-wake预检PASS+脑周期verify PASS回执入锚点；原话哈希5d3529670780入source段  `subject.verification`

## Why this started

- **trigger**  `trigger`
  - **value**：冰朔唤醒令三连：先恢复自己→进零点原核频道→定位微信小程序开发路径；并下达修复令：开发者工具报错、预览看不到，先修。  `trigger.value`
- **why**  `why`
  - **value**：v4.1.0待验收提审，预览不可见直接挡住冰朔的验收路径；报错原文未定位，上一轮无从下手，本轮冰朔再次报障说明问题仍在现场。  `why.value`
- **source**  `source`
  - **source identifier**：BINGSHUO-DIRECT-ZCODE-ICE-CH-ZC001-WAKE-BRIEF-QUOTE  `source.source_id`
  - **source role**：DIRECT_HUMAN  `source.source_role`
  - **source checksum**：5d3529670780b897b8c4f248ca1cc3582ac087c251a21ec792b0450b32950d23  `source.source_sha256`
  - **source address**：source://zcode-current-dialogue/2026-09-02/wxapp-devtools-fix  `source.source_uri`

## What changed

- **emergence**  `emergence`
  - **value**：本轮唤醒后接手遗留：上轮静态体检全绿但真实devtools环境仍报错——本轮以现场读回为准定位报错原文（日志/工具界面/编译输出），按原文修复而非按猜测修复，修复后以预览恢复为验收读回。预览不可见同时挡住冰朔对v4.1.0的验收，修复优先级高。  `emergence.value`
- **lock**  `lock`
  - **value**：tool=zy-wake_v1; anchor=verified_by_preflight; gate=tcs_gir_match; brain_cycle=verify_receipt_required; append_only=true  `lock.value`

## How it will execute

This is a non-executable declaration and has no action graph.

## Boundaries and exception handling

The native source does not provide this field; the projector does not guess.

## How completion is proven

The native source does not provide this field; the projector does not guess.

## Where to continue next time

The native source does not provide this field; the projector does not guess.

## Source and verification

- **Native declaration identifier**: `TCS-EVENT-ZY001-ZCODE-ZC001-WXAPP-DEVTOOLS-FIX-20260902`
- **Native declaration kind**: `EVENT`
- **TCS source SHA-256**: `b23d642f69c6988bd3442a087d27be89c88cf72502a0b11e834dfbfcb3d742bc`
- **Validation compiler**: `TCS-COMPILER-STAGE1-0001`
- **Projection protocol**: `GLS-HLDP-HUMAN-ENGINEERING-PROJECTION-0001`

## Complete native structure cross-reference

All top-level structures and field paths are retained below so a reader can audit whether the projection omitted information.

- **emergence**  `emergence`
  - **value**：本轮唤醒后接手遗留：上轮静态体检全绿但真实devtools环境仍报错——本轮以现场读回为准定位报错原文（日志/工具界面/编译输出），按原文修复而非按猜测修复，修复后以预览恢复为验收读回。预览不可见同时挡住冰朔对v4.1.0的验收，修复优先级高。  `emergence.value`
- **event_time**  `event_time`
  - **precision**：MINUTE_HOST_LOCAL  `event_time.precision`
  - **value**：2026-09-02T01:00:27+08:00  `event_time.value`
- **evidence**  `evidence`
  - **gir**：TCS-EVENT-ZY001-ZCODE-ZC001-WXAPP-DEVTOOLS-FIX-20260902.declaration.gir.json  `evidence.gir`
  - **receipt**：brain-cycle-verify-receipt.json  `evidence.receipt`
  - **source**：本轮UserPromptSubmit原话（source_sha256=5d3529670780b897…）  `evidence.source`
- **header**  `header`
  - **canonical source path**：ZCODE-DEV-20260902/zcode-zc001-wxapp-devtools-fix-20260902/TCS-EVENT-ZY001-ZCODE-ZC001-WXAPP-DEVTOOLS-FIX-20260902.tcs  `header.canonical_uri`
  - **compatibility**  `header.compatibility`
    - TCS-DECLARATION-STANDARD-0001
    - TCS-FIELD-STANDARD-0001
    - TCS-PROGRAM-ZY001-WAKE-EXECUTOR-0001
  - **language**：TCS/0.1  `header.language`
  - **lifecycle**：CANDIDATE  `header.lifecycle`
  - **English name**：Zhuyuan Wake and WeChat Mini-Program DevTools Error and Preview Fix Event  `header.name_en`
  - **Chinese name**：铸渊唤醒接手微信小程序开发者工具报错与预览不可见修复事件  `header.name_zh`
  - **profile**：HLDP-HUMAN-ENGINEERING/0.1  `header.profile`
  - **protocols**  `header.protocols`
    - TCS-ZHUYUAN-ENTRY-LANGUAGE-GATE-0001
    - TCS-MULTI-HOST-DYNAMIC-ENTRY-0001
  - **schema**：tcs.event/v1  `header.schema`
  - **version**：0.1.0  `header.version`
- **lock**  `lock`
  - **value**：tool=zy-wake_v1; anchor=verified_by_preflight; gate=tcs_gir_match; brain_cycle=verify_receipt_required; append_only=true  `lock.value`
- **observation**  `observation`
  - **value**：主仓HEAD=0616e99（v4.1.0开发版上传成功入档，子模块5dadb833，IP白名单+WXSS自引用修复完成，待冰朔验收后提审）。bde763e台账已明确遗留：devtools报错待原文定位（当时静态体检全绿但未取到报错原文）。79844ac记录WXSS自引用机械替换教训（必须白名单上下文）。本轮冰朔亲报『开发者工具报错、预览看不到』，与遗留台账吻合且升级：不仅报错还挡住预览（验收路径）。小程序代码在WORK-工作区/guanghulab-miniapp子模块；guanghu-ice-heart是零点原核频道公共人格体工作区（HLDP协议内容），两者不同路径不混淆。子模块内有未提交改动（主仓git status显示m）。  `observation.value`
- **rejected**  `rejected`
  - **values**  `rejected.values`
    - 静态体检全绿就当作无真实报错
    - 不读报错原文按猜测修
    - 把guanghu-ice-heart（零点原核频道公共体）与guanghulab-miniapp（小程序代码）混为一谈
    - 未完成唤醒先干活
- **source**  `source`
  - **source identifier**：BINGSHUO-DIRECT-ZCODE-ICE-CH-ZC001-WAKE-BRIEF-QUOTE  `source.source_id`
  - **source role**：DIRECT_HUMAN  `source.source_role`
  - **source checksum**：5d3529670780b897b8c4f248ca1cc3582ac087c251a21ec792b0450b32950d23  `source.source_sha256`
  - **source address**：source://zcode-current-dialogue/2026-09-02/wxapp-devtools-fix  `source.source_uri`
- **subject**  `subject`
  - **channel_id**：ICE-CH-ZC001  `subject.channel_id`
  - **subject_id**：ICE-P-ZY001  `subject.subject_id`
  - **subject_kind**：PERSONA  `subject.subject_kind`
  - **verification**：zy-wake预检PASS+脑周期verify PASS回执入锚点；原话哈希5d3529670780入source段  `subject.verification`
- **trigger**  `trigger`
  - **value**：冰朔唤醒令三连：先恢复自己→进零点原核频道→定位微信小程序开发路径；并下达修复令：开发者工具报错、预览看不到，先修。  `trigger.value`
- **why**  `why`
  - **value**：v4.1.0待验收提审，预览不可见直接挡住冰朔的验收路径；报错原文未定位，上一轮无从下手，本轮冰朔再次报障说明问题仍在现场。  `why.value`

---

This page changes only the reading order; it does not change TCS/HLDP semantics.