docs(security): add workflow secret audit templates

2026-05-19 00:57:38 +08:00
parent ad33b9dc06
commit f0a6e23a3c
34 changed files with 341 additions and 73 deletions
--- a/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md
+++ b/docs/security/AWOOOP-MIRROR-ONLY-CONSUMPTION-CHECKLIST.md
@@ -56,7 +56,7 @@ AwoooP 初期不得直接啟動掃描、不得呼叫 Codex patch runner、不得
 | `source_control_ref_truth_classification_v1` | refs diff 真相來源與 deprecated 候選分類；S4.11 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / 收件包 | Repo owner review queue、migration reviewer handoff | approval-only | 只顯示分類、1 個 request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、5 個 response templates 與人工判定隊列，不執行 sync/delete/force push |
 | `source_control_primary_readiness_gate_v1` | GitHub primary readiness / parity gate | Source-control review、Operator Console、Audit | approval-only | 只顯示 primary blockers、parity gates、rollback ADR 缺口；目前 `primary_ready_count=0` |
 | `source_control_primary_rollback_adr_v1` | GitHub primary rollback ADR 草案與 validation window | Source-control review、Operator Console、Audit | approval-only | 只顯示 7 個 repo 的 rollback draft、owner review、validation window；不得執行 rollback 或切 primary |
-| `source_control_workflow_secret_name_inventory_v1` | workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory gate；S4.12 owner response 收件包 | Source-control review、Secret hygiene audit、Operator Console | approval-only | 只顯示缺口、S4.2 local evidence、S4.3 redacted export request、S4.12 owner response request packet、5 個 template statuses 與 5 個 response templates；目前 `inventory_complete_count=0`，不得保存 secret value |
+| `source_control_workflow_secret_name_inventory_v1` | workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory gate；S4.12 owner response 收件包 | Source-control review、Secret hygiene audit、Operator Console | approval-only | 只顯示缺口、S4.2 local evidence、S4.3 redacted export request、S4.12 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 response templates；目前 `inventory_complete_count=0`，不得保存 secret value |
 | `local_repo_canonical_probe_v1` | 本機 working tree lineage 比對 | Canonical decision evidence | mirror-only | 不自動合併、不自動建 repo、不刪除 |
 | `git_remote_refs_probe_v1` | 指定 repo remote refs read-only probe | Source readiness evidence | mirror-only | 不 fetch、不 push、不自動 mirror |
 | `approval_required_event_v1` | 上述事件的高風險 gate | Approval queue、Audit | approval-only | `blocked_until_approved=true` |
@@ -129,7 +129,7 @@ AwoooP 初期不得直接啟動掃描、不得呼叫 Codex patch runner、不得
 | `source_control_reconcile_plan_v1.status=draft_blocked` | `approve_required` | 只顯示 refs reconcile 草案與 gate，不執行 sync |
 | `source_control_ref_detail_diff_v1.status=draft_blocked` | `observe` | 顯示 branch/tag 明細 diff，支援人工 review |
 | `source_control_ref_truth_classification_v1.status=draft_blocked` | `approve_required` | 顯示 main/dev 真相來源、drift deprecated 候選、release / UAT tag review lane、S4.11 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 templates；不執行分類結果 |
-| `source_control_workflow_secret_name_inventory_v1.status=draft_missing_evidence` | `approve_required` | 顯示 S4.2 local evidence、S4.3 export request、S4.12 owner response request packet、template status ledger 與 templates；不收 secret value、不改 workflow、不啟用 runner |
+| `source_control_workflow_secret_name_inventory_v1.status=draft_missing_evidence` | `approve_required` | 顯示 S4.2 local evidence、S4.3 export request、S4.12 owner response request packet、template status ledger、audit event templates 與 templates；不收 secret value、不改 workflow、不啟用 runner |
 | `local_repo_canonical_probe_v1.status=unrelated` | `approve_required` | 禁止自動合併，需人工 canonical 判定 |
 | `git_remote_refs_probe_v1.status=ok` | `observe` | 可作 source evidence，但仍需 GitHub target 與 approval |
 | `security_rollout_policy_v1.enforcement_level=mirror_only` | `observe` | 只顯示 policy，不阻擋既有流程 |
@@ -219,6 +219,6 @@ AwoooP 初期不得直接啟動掃描、不得呼叫 Codex patch runner、不得
 3. AwoooP 先 mirror S4.13 owner response validation rollup，集中顯示 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets；不得把 rollup 視為 approval 或 execution authorization。
 4. Security Supply Chain Session 依 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 7 個 GitHub target owner / visibility / canonical response。
 5. Security Supply Chain Session 依 S4.11 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 5 個 refs truth owner response templates；audit event templates 目前 0 emitted，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，preflight 只分類可審、補證、隔離、拒收或等待，response 通過也只更新 read-only classification / reconcile / readiness wording。
-6. Security Supply Chain Session 依 S4.12 request packet / template status ledger 收到並驗收 5 個 workflow / secret 名稱 owner response templates；request packet 只提示 owner 要回覆什麼，template status ledger 只逐項顯示 waiting，response 通過也只更新 read-only inventory / export request / readiness wording。
+6. Security Supply Chain Session 依 S4.12 request packet / template status ledger / audit event templates 收到並驗收 5 個 workflow / secret 名稱 owner response templates；request packet 只提示 owner 要回覆什麼，template status ledger 只逐項顯示 waiting，audit event templates 只定義 0 emitted 的脫敏 metadata，response 通過也只更新 read-only inventory / export request / readiness wording。
 7. AwoooP 只建立 mirror/read-only policy 入口，不新增 execution action。
 8. 任一方要把事件升級成實際執行，都必須先產出 `approval_required_event_v1`，並在 `security_approval_queue_v1` 中維持 `blocked_until_approved=true` 直到人工決策完成。
--- a/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md
+++ b/docs/security/AWOOOP-SECURITY-SUPPLYCHAIN-INTEGRATION-HANDOFF.md
@@ -297,9 +297,9 @@ S4.2 local evidence：已新增本機只讀 collector 與 snapshot，7 個 local

 S4.3 export request：已新增 `source_control_workflow_secret_name_export_request_v1` supporting schema、snapshot 與人讀版；7 個 in-scope repos、5 類 export lanes：webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity。`write_token_allowed=false`、`secret_value_collection_allowed=false`。

-S4.12 owner response：已新增 `source_control_workflow_secret_name_owner_response_v1` supporting schema、snapshot 與人讀版；1 個 owner response request packet、5 個 template statuses 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity。`received_response_count=0`、`accepted_response_count=0`、`secret_value_collection_allowed=false`、`write_token_allowed=false`。
+S4.12 owner response：已新增 `source_control_workflow_secret_name_owner_response_v1` supporting schema、snapshot 與人讀版；1 個 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity。`received_response_count=0`、`accepted_response_count=0`、`audit_events_emitted=0`、`secret_value_collection_allowed=false`、`write_token_allowed=false`。

-AwoooP 初期處理方式：只顯示 inventory lane 缺口、S4.2 local evidence、S4.3 export request、S4.12 owner response request packet / template status ledger / templates、要求 redacted snapshot 與人工 review；不得收集 secret value、修改 workflow、rotate secret、啟用 GitHub hosted runner、sync refs 或切 GitHub primary。
+AwoooP 初期處理方式：只顯示 inventory lane 缺口、S4.2 local evidence、S4.3 export request、S4.12 owner response request packet / template status ledger / audit event templates / templates、要求 redacted snapshot 與人工 review；不得收集 secret value、修改 workflow、rotate secret、啟用 GitHub hosted runner、sync refs 或切 GitHub primary。

 ### `security_mirror_readiness_v1`

@@ -393,7 +393,7 @@ Schema：`docs/schemas/security_mirror_status_rollup_v1.schema.json`

 Snapshot：`docs/security/security-mirror-status-rollup.snapshot.json`

-目前 rollup：`framework_ready_waiting_approval`；35 個 contracts、32 ready、2 partial、1 contract-only、0 blocked；approval queue 仍為 8 items，其中 7 pending approval、1 block candidate；review packets 8 筆；state transition rules 5 筆；follow-up runtime gate templates 8 筆；active runtime gates 0 筆；GitHub primary candidate repos 8 筆、primary ready 0 筆；S4.4 rollback ADR repo plans 7 筆、owner approved 0 筆、dry-run completed 0 筆；S4.10 GitHub target owner response request packet 1 筆、template statuses 7 筆、audit event templates 3 筆、redaction examples 5 筆、collection checks 6 筆、intake preflight checks 6 筆、owner decision response templates 7 筆、received response 0 筆、accepted response 0 筆；S4.11 refs truth owner response request packet 1 筆、template statuses 5 筆、audit event templates 3 筆、redaction examples 5 筆、collection checks 6 筆、intake preflight checks 6 筆、templates 5 筆、received response 0 筆、accepted response 0 筆、audit events emitted 0 筆；Gitea inventory 目前 `partial_waiting_authenticated_inventory`，public-only repo 2 個、本機可見 Gitea unique repo 4 個、export source options 2 類、S4.6 import acceptance payload 0 筆、S4.7 owner attestation items 5 筆、received attestation 0 筆、S4.9 owner response request packet 1 筆、template statuses 5 筆、audit event templates 3 筆、redaction examples 5 筆、display sections 8 筆、collection checks 6 筆、S4.9 owner response templates 5 筆、intake preflight checks 6 筆、outcome lanes 5 筆、received response 0 筆、audit events emitted 0 筆、quarantine required=true、token value collection allowed=false；workflow / secret 名稱 inventory candidate repos 8 筆、complete 0 筆、S4.12 owner response request packet 1 筆、S4.12 template statuses 5 筆、S4.12 owner response templates 5 筆、received response 0 筆、accepted response 0 筆；S4.2 local evidence repos 4 筆、workflow files 31 筆、referenced secret names 43 筆；decision records 目前 0 筆。
+目前 rollup：`framework_ready_waiting_approval`；35 個 contracts、32 ready、2 partial、1 contract-only、0 blocked；approval queue 仍為 8 items，其中 7 pending approval、1 block candidate；review packets 8 筆；state transition rules 5 筆；follow-up runtime gate templates 8 筆；active runtime gates 0 筆；GitHub primary candidate repos 8 筆、primary ready 0 筆；S4.4 rollback ADR repo plans 7 筆、owner approved 0 筆、dry-run completed 0 筆；S4.10 GitHub target owner response request packet 1 筆、template statuses 7 筆、audit event templates 3 筆、redaction examples 5 筆、collection checks 6 筆、intake preflight checks 6 筆、owner decision response templates 7 筆、received response 0 筆、accepted response 0 筆；S4.11 refs truth owner response request packet 1 筆、template statuses 5 筆、audit event templates 3 筆、redaction examples 5 筆、collection checks 6 筆、intake preflight checks 6 筆、templates 5 筆、received response 0 筆、accepted response 0 筆、audit events emitted 0 筆；Gitea inventory 目前 `partial_waiting_authenticated_inventory`，public-only repo 2 個、本機可見 Gitea unique repo 4 個、export source options 2 類、S4.6 import acceptance payload 0 筆、S4.7 owner attestation items 5 筆、received attestation 0 筆、S4.9 owner response request packet 1 筆、template statuses 5 筆、audit event templates 3 筆、redaction examples 5 筆、display sections 8 筆、collection checks 6 筆、S4.9 owner response templates 5 筆、intake preflight checks 6 筆、outcome lanes 5 筆、received response 0 筆、audit events emitted 0 筆、quarantine required=true、token value collection allowed=false；workflow / secret 名稱 inventory candidate repos 8 筆、complete 0 筆、S4.12 owner response request packet 1 筆、S4.12 template statuses 5 筆、S4.12 audit event templates 3 筆、S4.12 owner response templates 5 筆、received response 0 筆、accepted response 0 筆、audit events emitted 0 筆；S4.2 local evidence repos 4 筆、workflow files 31 筆、referenced secret names 43 筆；decision records 目前 0 筆。

 AwoooP 初期處理方式：只顯示階段狀態、下一個 gate 與禁止事項，可寫入 Audit evidence；不得把 rollup 當 runtime authorization。

@@ -911,7 +911,7 @@ Console 初期不提供高風險執行按鈕。

 2026-05-13 S4.3 workflow / secret name redacted export request 追加：已新增 `docs/schemas/source_control_workflow_secret_name_export_request_v1.schema.json`、`docs/security/source-control-workflow-secret-name-export-request.snapshot.json` 與 `docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md`。本輪只定義 7 個 in-scope repos、5 類 export lanes 的 owner / read-only export 欄位與拒收規則：webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；`write_token_allowed=false`、`secret_value_collection_allowed=false`，不得呼叫 API 或修改 GitHub/Gitea。

-2026-05-17 S4.12 workflow / secret name owner response 追加，2026-05-19 補 request packet 與 template status ledger：已新增 `docs/schemas/source_control_workflow_secret_name_owner_response_v1.schema.json`、`docs/security/source-control-workflow-secret-name-owner-response.snapshot.json` 與 `docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md`。目前 1 個 owner response request packet、5 個 template statuses 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；received / accepted response 皆為 0。AwoooP 可 mirror 成 owner response intake queue，但不得把 request packet、template status ledger 或 response packet 當成 secret value collection、workflow modification、GitHub hosted runner enablement 或 GitHub primary approval。
+2026-05-17 S4.12 workflow / secret name owner response 追加，2026-05-19 補 request packet、template status ledger 與 audit event templates：已新增 `docs/schemas/source_control_workflow_secret_name_owner_response_v1.schema.json`、`docs/security/source-control-workflow-secret-name-owner-response.snapshot.json` 與 `docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md`。目前 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；received / accepted response 皆為 0、audit events emitted 仍為 0。AwoooP 可 mirror 成 owner response intake queue，但不得把 request packet、template status ledger、audit event templates 或 response packet 當成 secret value collection、workflow modification、GitHub hosted runner enablement 或 GitHub primary approval。

 2026-05-17 S4.13 owner response validation rollup 追加：已新增 `docs/schemas/source_control_owner_response_validation_rollup_v1.schema.json`、`docs/security/source-control-owner-response-validation-rollup.snapshot.json` 與 `docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md`。目前彙整 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets，22 個 response templates、received / accepted / rejected response 皆為 0、cross-packet checks 10 個。AwoooP 可 mirror 成只讀驗收總覽，但不得把 rollup 當成 approval、runtime gate、repo / refs / workflow / secret / runner 執行授權或 GitHub primary approval。

--- a/docs/security/GITEA-GITHUB-MIGRATION-INVENTORY.md
+++ b/docs/security/GITEA-GITHUB-MIGRATION-INVENTORY.md
@@ -52,7 +52,7 @@
 - GitHub target 決策表已建立，8 個候選中 7 個需人工批准；其中 `ewoooc`、`bitan-pharmacy`、`tsenyang-website` 在 target visibility / owner 決策前不得自動建立或同步。
 - GitHub target repo-by-repo approval package 已建立，7 個 approval-required targets 拆成 refs reconcile、target 建立 / 授權、internal remote 用途確認三條路徑；此 package 採低摩擦原則，只 gate 高風險執行，不阻擋 read-only evidence。
 - Source Control ref truth classification 已建立，141 個 refs review items 已拆成 4 個真相來源判定、114 個 drift deprecated 候選、3 個 release tag review、20 個 GitHub-only refs review；S4.11 已補 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與 5 個 owner response templates，received / accepted response 皆為 0、audit events emitted 仍為 0。這是人工判定隊列與收件框架，不是同步批准。
- Workflow / secret 名稱 owner response 已建立，S4.12 補 1 個 owner response request packet、5 個 template statuses 與 5 個 response templates，received / accepted response 皆為 0；這只允許 owner 補 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted disposition，不授權收 secret value、修改 workflow、啟用 GitHub hosted runner 或切 GitHub primary。
+- Workflow / secret 名稱 owner response 已建立，S4.12 補 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 response templates，received / accepted response 皆為 0、audit events emitted 仍為 0；這只允許 owner 補 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted disposition，不授權收 secret value、修改 workflow、啟用 GitHub hosted runner 或切 GitHub primary。
 - Owner response validation rollup 已建立，S4.13 彙整 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets，共 22 個 response templates、received / accepted response 皆為 0；這只是驗收總覽，不是 approval、runtime gate 或執行授權。
 - 本機可見 Git working tree 輔助盤點已找到 13 個 repo，其中去重後 Gitea repo 4 個、GitHub repo 5 個、110 內部 repo 4 個；此結果可用來補遷移矩陣，但不能取代 Gitea server 全量清單。

@@ -229,7 +229,7 @@ GitHub target repo-by-repo approval package 已建立於 `docs/security/GITHUB-T
 2. 依 `github_target_decision_v1` 對需要人工批准的 target 做 owner / visibility / canonical 決策。
 3. 依 `docs/security/SOURCE-CONTROL-REF-TRUTH-CLASSIFICATION.md` 由 repo owner 對 main/dev、release tags、GitHub-only refs 與 drift deprecated 候選逐項判定；仍不 push refs。
 4. 標記「可 mirror」、「需人工判斷」、「需封存」、「不可搬」。
-5. 依 S4.12 workflow / secret name owner response request packet、template status ledger 與收件包驗收 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；仍不得收 secret value、改 workflow 或啟用 hosted runner。
+5. 依 S4.12 workflow / secret name owner response request packet、template status ledger、audit event templates 與收件包驗收 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；仍不得收 secret value、改 workflow 或啟用 hosted runner。
 6. 依 S4.13 owner response validation rollup 集中檢查 S4.9-S4.12 四包 response validation；仍不得把 rollup 當 approval 或 execution authorization。
 7. 產出 GitHub primary ADR，定義切換 gate 與 rollback。
 8. 將 `source_control_migration_event_v1`、`gitea_repo_inventory_v1`、`local_git_remote_inventory_v1` mirror 到 AwoooP，初期只作為 evidence。
--- a/docs/security/SECURITY-APPROVAL-GATE.md
+++ b/docs/security/SECURITY-APPROVAL-GATE.md
@@ -38,7 +38,7 @@ S3.1 開始，實際人工決策紀錄由 `security_approval_decision_record_v1`
 | 1 | Redacted finding ingestion | 只批准設計或 draft PR |
 | 2 | Safe web crawl | 只批准低噪音 scope 定義 |
 | 3 | Gitea owner attestation + read-only inventory | 先依 S4.9 驗收 S4.7 owner response，再只批准只讀 inventory 或 redacted admin export |
-| 4 | GitHub target decisions | 只批准逐 repo S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response 與 S4.12 request packet / template status ledger / workflow secret 名稱 response 驗收與決策草案 |
+| 4 | GitHub target decisions | 只批准逐 repo S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response 與 S4.12 request packet / template status ledger / audit event templates / workflow secret 名稱 response 驗收與決策草案 |
 | 5 | Ref truth review | 只批准 S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response 驗收、人工分類與 reconcile 草案 |
 | 6 | Credentialed scan | 只允許人工 exception 設計，仍需 runtime gate |
 | 7 | Kali full-upgrade / reboot | 只允許維護窗口與 rollback 規劃 |
--- a/docs/security/SECURITY-APPROVAL-QUEUE.md
+++ b/docs/security/SECURITY-APPROVAL-QUEUE.md
@@ -35,7 +35,7 @@ S3.0 開始，人工批准範圍由 `security_approval_gate_v1` 承接。S3.1
 | 1 | `kali-finding-runtime-ingestion-approval-20260513` | 先接 redacted finding evidence，風險低、價值高 |
 | 2 | `kali-safe-web-crawl-approval-20260513` | TLS/header/basic crawl 屬低噪音，但仍需批准 scope |
 | 3 | `gitea-private-internal-server-side-inventory-2026-05-12` | 先依 S4.9 收到並驗收 S4.7 owner coverage attestation response，再審 Gitea 全量版本轉 GitHub 的只讀 inventory gate |
-| 4 | `source-control-target-repo-approval-bundle-20260513` | 先依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 驗收逐 repo owner / visibility / canonical response，並依 S4.12 request packet / template status ledger 驗收 workflow / secret 名稱 owner response |
+| 4 | `source-control-target-repo-approval-bundle-20260513` | 先依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 驗收逐 repo owner / visibility / canonical response，並依 S4.12 request packet / template status ledger / audit event templates 驗收 workflow / secret 名稱 owner response |
 | 5 | `source-control-ref-truth-review-bundle-20260513` | 先依 S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 驗收 refs truth owner response，再看 deprecated / release tag review |
 | 6 | `kali-credentialed-scan-approval-20260513` | 需要憑證，風險較高 |
 | 7 | `kali-full-upgrade-reboot-approval-20260513` | 需要維護窗口、snapshot、rollback 與 post-check |
--- a/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md
+++ b/docs/security/SECURITY-APPROVAL-REVIEW-PACKET.md
@@ -39,7 +39,7 @@ S3.4 開始，等待 runtime gate 時要看哪些前置條件，由 `security_fo
 | 1 | Redacted finding ingestion | `design_or_draft_review` | 只審是否可設計或建立 draft PR |
 | 2 | Safe web crawl | `low_noise_scan_scope_review` | 只審低噪音 scope 定義 |
 | 3 | Gitea owner attestation + read-only inventory | `read_only_inventory_review` | 先依 S4.9 審 S4.7 owner response，再審只讀 token 或 redacted export |
-| 4 | GitHub target decisions | `design_or_draft_review` | 先審 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response 與 S4.12 workflow / secret 名稱 request packet / template status ledger / response，再審 owner / visibility / canonical 草案 |
+| 4 | GitHub target decisions | `design_or_draft_review` | 先審 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response 與 S4.12 workflow / secret 名稱 request packet / template status ledger / audit event templates / response，再審 owner / visibility / canonical 草案 |
 | 5 | Ref truth review | `design_or_draft_review` | 先審 S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response 驗收，再審人工分類與 reconcile 草案 |
 | 6 | Credentialed scan | `manual_exception_review` | 只審 exception 設計 |
 | 7 | Kali full-upgrade / reboot | `manual_exception_review` | 只審維護窗口與 rollback 計畫 |
--- a/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md
+++ b/docs/security/SECURITY-FOLLOWUP-RUNTIME-GATE.md
@@ -34,7 +34,7 @@
 | Redacted finding ingestion | MEDIUM | 只準備 ingestion adapter 的 redaction / audit 前置條件 |
 | Safe web crawl scope | MEDIUM | 只準備 TLS/header/basic crawl 的低噪音 scope |
 | Gitea owner attestation + read-only inventory | MEDIUM | 先依 S4.9 驗收 S4.7 owner response，再準備 read-only token 或 redacted export inventory |
-| GitHub target decision | HIGH | 只準備 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response、S4.12 workflow / secret 名稱 request packet / template status ledger / response 驗收、owner / visibility / canonical / workflow parity 決策 |
+| GitHub target decision | HIGH | 只準備 S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / response、S4.12 workflow / secret 名稱 request packet / template status ledger / audit event templates / response 驗收、owner / visibility / canonical / workflow parity 決策 |
 | Ref truth review | HIGH | 只準備 S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response 驗收、refs truth / deprecated / release tag 人工判定 |
 | Credentialed scan exception | HIGH | 只準備人工 exception、credential lifecycle 與停用方式 |
 | Kali full-upgrade / reboot | HIGH | 只準備維護窗口、snapshot、rollback 與 post-health |
--- a/docs/security/SECURITY-MIRROR-DRY-RUN.md
+++ b/docs/security/SECURITY-MIRROR-DRY-RUN.md
@@ -24,7 +24,7 @@
 | `CHECK_ROUTE_COVERAGE` | 確認 route groups 覆蓋所有 contracts | 不建立 fallback execution route |
 | `CHECK_ACCEPTANCE_AND_QUARANTINE` | 確認驗收與隔離只處理 mirror payload | 不阻擋 runtime |
 | `CHECK_PROGRESS_GUARD` | 確認 58% headline 進度與 micro progress delta ledger 只作狀態顯示 | 不把進度或 delta ledger 當 approval 或 runtime authorization |
-| `CHECK_OWNER_RESPONSE_GUARD` | 確認四包 owner response 仍未收到 / 接受，且 S4.9 request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / preflight / outcome lanes 只提示 owner、逐項顯示 waiting、只定義 0 emitted 的 metadata audit 模板、脫敏範例與只讀 UI 區塊、維持收件狀態分離、分類可審、補證、隔離、拒收或等待；S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 也只提示 7 個 GitHub target 要回覆的欄位、逐項顯示 waiting / request ready、定義 0 emitted 的脫敏 metadata、維持 request / received / accepted 分離，並只分類可收、補證、隔離或拒收；S4.11 request packet 只提示 5 類 refs truth owner response 欄位，template status ledger 逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，intake preflight checks 只分類可審、補證、隔離、拒收或等待 | 不把 guard pass、request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo、refs、workflow、secret、runner、primary、audit production ingestion 或 runtime 授權 |
+| `CHECK_OWNER_RESPONSE_GUARD` | 確認四包 owner response 仍未收到 / 接受，且 S4.9 request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / preflight / outcome lanes 只提示 owner、逐項顯示 waiting、只定義 0 emitted 的 metadata audit 模板、脫敏範例與只讀 UI 區塊、維持收件狀態分離、分類可審、補證、隔離、拒收或等待；S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 也只提示 7 個 GitHub target 要回覆的欄位、逐項顯示 waiting / request ready、定義 0 emitted 的脫敏 metadata、維持 request / received / accepted 分離，並只分類可收、補證、隔離或拒收；S4.11 request packet 只提示 5 類 refs truth owner response 欄位，template status ledger 逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，intake preflight checks 只分類可審、補證、隔離、拒收或等待；S4.12 request packet 只提示 5 類 workflow / secret 名稱 owner response 欄位，template status ledger 逐項顯示 waiting / request ready，audit event templates 只定義 0 emitted 的脫敏 metadata | 不把 guard pass、request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo、refs、workflow、secret、runner、primary、audit production ingestion 或 runtime 授權 |
 | `CHECK_LOW_NOISE_CHANNEL` | 確認 Channel Event 低噪音 | 不對 LOW / MEDIUM 洗版 |
 | `CONFIRM_NO_RUNTIME_ACTION` | 確認 dry-run 沒有任何 runtime action | 不掃描、不 deploy、不 sync refs |

--- a/docs/security/SECURITY-MIRROR-READINESS.md
+++ b/docs/security/SECURITY-MIRROR-READINESS.md
@@ -91,7 +91,7 @@ GitHub target 決策面需同時 mirror S4.10 `GITHUB-TARGET-OWNER-DECISION-RESP

 Ref truth 決策面需同時 mirror S4.11 `SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md` 與 `source-control-ref-truth-owner-response.snapshot.json`，只顯示 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、5 個 owner response templates、received / accepted response 皆為 0、audit events emitted 仍為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 refs sync、delete、force push 或 GitHub primary approval。

-Workflow / secret 名稱決策面需同時 mirror S4.12 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` 與 `source-control-workflow-secret-name-owner-response.snapshot.json`，只顯示 1 個 owner response request packet、5 個 template statuses、5 個 owner response templates、received / accepted response 皆為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 request packet、template status ledger 或 response packet 當成 secret value 收集、workflow 修改、GitHub hosted runner 啟用或 GitHub primary approval。
+Workflow / secret 名稱決策面需同時 mirror S4.12 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` 與 `source-control-workflow-secret-name-owner-response.snapshot.json`，只顯示 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 owner response templates、received / accepted response 皆為 0、audit events emitted 仍為 0、8 個 acceptance checks 與 10 個 rejection rules；不得把 request packet、template status ledger、audit event templates 或 response packet 當成 secret value 收集、workflow 修改、GitHub hosted runner 啟用或 GitHub primary approval。

 Owner response validation 決策面需同時 mirror S4.13 `SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md` 與 `source-control-owner-response-validation-rollup.snapshot.json`，只顯示 S4.9 / S4.10 / S4.11 / S4.12 四個 response packets 的驗收總覽：22 個 templates、received / accepted / rejected 皆為 0、cross-packet checks 10 個；不得把 rollup 當成 approval、runtime gate 或 execution authorization。

--- a/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md
+++ b/docs/security/SECURITY-MIRROR-STATUS-ROLLUP.md
@@ -28,10 +28,10 @@
 | Review packets | S3.2 已建立；8 packets、7 ready for human review、1 block candidate |
 | State transitions | S3.3 已建立；5 個 decision options 都有 next state，且都不授權執行 |
 | Follow-up runtime gate templates | S3.4 已建立；8 個 templates、0 個 active runtime gates |
-| GitHub primary readiness gate | S4.0 已建立；8 個 candidate repos、7 個 in-scope blocked、0 個 primary ready；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包，7 個 response templates、owner response 0 筆；S4.11 已補 refs truth owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包，5 個 response templates、owner response 0 筆、audit events emitted 0 筆；S4.12 已補 workflow / secret 名稱 owner response request packet、5 個 template statuses 與收件包，5 個 response templates、owner response 0 筆；S4.13 已補四包 owner response validation rollup，22 個 templates、received / accepted / rejected 皆為 0 |
+| GitHub primary readiness gate | S4.0 已建立；8 個 candidate repos、7 個 in-scope blocked、0 個 primary ready；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包，7 個 response templates、owner response 0 筆；S4.11 已補 refs truth owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包，5 個 response templates、owner response 0 筆、audit events emitted 0 筆；S4.12 已補 workflow / secret 名稱 owner response request packet、5 個 template statuses、3 個 audit event templates 與收件包，5 個 response templates、owner response 0 筆、audit events emitted 0 筆；S4.13 已補四包 owner response validation rollup，22 個 templates、received / accepted / rejected 皆為 0 |
 | GitHub primary rollback ADR | S4.4 已建立；7 個 in-scope rollback drafts、0 個 owner approved、0 個 dry-run completed、0 個 active cutover |
 | Gitea inventory | S4.5 已補認證清冊匯出請求；S4.6 已補匯入驗收契約；S4.7 已補 owner coverage attestation；S4.8 已把既有 Gitea queue/gate/review packet/follow-up gate 對齊 attestation 先行；S4.9 已補 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response 收件包、6 個 intake preflight checks 與 5 個 outcome lanes；目前 status=`partial_waiting_authenticated_inventory`、未認證公開範圍 repos 2 個、本機可見 Gitea unique repos 4 個、匯出來源選項 2 類、匯入驗收 payload 0 筆、owner attestation items 5 個、收到 attestation 0 筆、owner response 0 筆、audit events emitted 0 筆、敏感 payload 必須隔離、允許收集 token value=false |
-| Workflow / secret name inventory | S4.1 已建立；S4.2 補 4 個 repos、31 個 workflow files、43 個 referenced secret names 的 local evidence；S4.3 補 7 個 repos、5 類 lanes 的 redacted export request；S4.12 補 1 個 owner response request packet、5 個 template statuses 與 5 個 owner response templates；0 個 inventory complete、禁止收集 secret value、禁止 write token |
+| Workflow / secret name inventory | S4.1 已建立；S4.2 補 4 個 repos、31 個 workflow files、43 個 referenced secret names 的 local evidence；S4.3 補 7 個 repos、5 類 lanes 的 redacted export request；S4.12 補 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 owner response templates；0 個 inventory complete、audit events emitted 0 筆、禁止收集 secret value、禁止 write token |
 | Owner response validation | S4.13 已建立；四包 owner response 目前 received/accepted 皆為 0；4 條 missing response lanes、4 步 collection order 與 next collection candidate 可供 AwoooP 直接顯示；下一個建議收件為 S4.9 Gitea owner attestation；latest local validation 為 `SOURCE_CONTROL_OWNER_RESPONSE_GUARD_OK`，不代表 owner response 已收到或任何執行授權 |
 | Dry-run | `contract_defined_not_executed`；已納入 `CHECK_PROGRESS_GUARD` 與 `CHECK_OWNER_RESPONSE_GUARD`，latest local validation 為 `repo_snapshot_guard_pass`，仍不代表 production ingestion |
 | Runtime actions | `false` |
@@ -66,6 +66,7 @@
 | S4.11 intake preflight checks | framework detail | 0 | 只分類可審、補證、隔離、拒收或等待，不代表 owner response accepted 或 refs sync/delete/force push 授權 |
 | S4.12 request packet | framework detail | 0 | 只顯示 owner 要回覆哪 5 類 workflow / secret 名稱問題，不代表 request sent、response received、secret value collection、workflow 修改、runner 啟用或 primary 授權 |
 | S4.12 template status ledger | framework detail | 0 | 只逐項顯示 5 類 workflow / secret 名稱 response 仍為 waiting，received / accepted 仍為 0，不代表 secret value collection、workflow 修改、runner 啟用或 primary 授權 |
+| S4.12 audit event templates | framework detail | 0 | event templates 仍為 `template_only_not_emitted`，emitted 仍為 0，不代表 production ingestion、secret value collection、workflow 修改、runner 啟用或 primary 授權 |

 headline 進度要再往上，至少需要下列任一高層 gate 有實質 evidence：

@@ -112,10 +113,10 @@ python3 scripts/security/security-mirror-progress-guard.py
 4. GitHub target / owner / visibility / canonical：先依 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 7 個 owner decision response templates；received / accepted response 目前皆為 0，不得把 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo creation、visibility change、refs sync 或 primary approval。
 5. Kali `/execute` 維持 block candidate。
 6. Refs truth owner response：先依 S4.11 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 顯示 main/dev truth、deprecated drift、release tag、GitHub-only refs 的 5 個 response templates；received / accepted response 目前皆為 0，audit events emitted 仍為 0，不得把 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 refs sync、delete、force push 或 primary approval。
-7. Workflow / secret 名稱 owner response：先依 S4.12 request packet 與 template status ledger 顯示 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 5 個 response templates；received / accepted response 目前皆為 0，不得把 request packet、template status ledger 或 response packet 當成 secret value 收集、workflow 修改、GitHub hosted runner 啟用或 primary approval。
+7. Workflow / secret 名稱 owner response：先依 S4.12 request packet、template status ledger 與 audit event templates 顯示 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 5 個 response templates；received / accepted response 目前皆為 0，audit events emitted 仍為 0，不得把 request packet、template status ledger、audit event templates 或 response packet 當成 secret value 收集、workflow 修改、GitHub hosted runner 啟用或 primary approval。
 8. Owner response validation rollup：先依 S4.13 顯示 S4.9/S4.10/S4.11/S4.12 四包 response packets、22 個 templates、10 個 cross-packet checks 與 quarantine rules；不得把 rollup 當成 approval、runtime gate 或 execution authorization。
 9. GitHub primary readiness blockers 與 rollback ADR 缺口。
 10. S4.4 GitHub primary rollback ADR 草案：先顯示 7 個 repo 的 rollback owner、validation window 與 triggers，owner approval 前不可執行。
-11. workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 缺口，先看 S4.2 local evidence，再依 S4.3 redacted export request 與 S4.12 owner response request packet / template status ledger / 收件包補 webhook / runner / deploy key / branch protection / repository secret parity；只保存名稱與 owner，不保存 value，不使用 write token。
+11. workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 缺口，先看 S4.2 local evidence，再依 S4.3 redacted export request 與 S4.12 owner response request packet / template status ledger / audit event templates / 收件包補 webhook / runner / deploy key / branch protection / repository secret parity；只保存名稱與 owner，不保存 value，不使用 write token。

 任何批准後的執行仍需下一階段 runtime gate 與獨立 evidence，不得由本 rollup 自動觸發。
--- a/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md
+++ b/docs/security/SECURITY-SUPPLY-CHAIN-CONTRACT-MANIFEST.md
@@ -50,7 +50,7 @@
 | `source_control_ref_truth_classification_v1` | approval-only | refs diff 的真相來源候選與 deprecated 候選分類；S4.11 已補 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，5 templates、received 0、audit events emitted 0 | `source-control-ref-truth-classification.snapshot.json` / `source-control-ref-truth-owner-response.snapshot.json` |
 | `source_control_primary_readiness_gate_v1` | approval-only | GitHub primary readiness / parity gate | `source-control-primary-readiness-gate.snapshot.json` |
 | `source_control_primary_rollback_adr_v1` | approval-only | GitHub primary rollback ADR 草案與 validation window | `source-control-primary-rollback-adr.snapshot.json` |
-| `source_control_workflow_secret_name_inventory_v1` | approval-only | workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory gate；S4.2 已補 local evidence，S4.3 已補 redacted export request，S4.12 已補 owner response request packet、template status ledger 與收件包 | `source-control-workflow-secret-name-inventory.snapshot.json` / `source-control-workflow-secret-name-local-evidence.snapshot.json` / `source-control-workflow-secret-name-export-request.snapshot.json` / `source-control-workflow-secret-name-owner-response.snapshot.json` |
+| `source_control_workflow_secret_name_inventory_v1` | approval-only | workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory gate；S4.2 已補 local evidence，S4.3 已補 redacted export request，S4.12 已補 owner response request packet、template status ledger、audit event templates 與收件包 | `source-control-workflow-secret-name-inventory.snapshot.json` / `source-control-workflow-secret-name-local-evidence.snapshot.json` / `source-control-workflow-secret-name-export-request.snapshot.json` / `source-control-workflow-secret-name-owner-response.snapshot.json` |
 | `local_repo_canonical_probe_v1` | mirror-only | momo/ewoooc lineage evidence | `local-repo-canonical-ewoooc-momo.snapshot.json` |
 | `git_remote_refs_probe_v1` | mirror-only | 110 / GitHub remote refs readiness | `bitan-tsenyang`、`wooo-infra-config` |
 | `approval_required_event_v1` | approval-only | 高風險 / 敏感邊界 approval | `gitea-readonly-inventory-approval.snapshot.json` |
@@ -62,7 +62,7 @@
 3. 將 snapshot mirror 成 Runtime State / Channel Event / Audit evidence。
 4. 讀到 `source-control-ref-truth-owner-response.snapshot.json` 時，只顯示 S4.11 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、response templates、acceptance checks 與 rejection rules；不得新增 refs action。
 5. 讀到 `source-control-owner-response-validation-rollup.snapshot.json` 時，只顯示 S4.9/S4.10/S4.11/S4.12 四個 response packets 的總覽：22 個 templates、received / accepted / rejected 皆為 0、cross-packet checks 10 個；不得把 rollup 當成 approval 或 execution authorization。
-6. 只對 `approval_required_event_v1`、repo approval package、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1` 與 `source_control_workflow_secret_name_inventory_v1` 建 approval candidate / review lane / next-state display / runtime gate preparation / primary readiness display / rollback ADR display / workflow-secret name inventory gate / redacted export request display；`github_target_decision_v1` 只能顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、owner decision response templates、received_response_count=0、acceptance checks 與 rejection rules，不得觸發 repo creation、visibility change、refs sync 或 primary switch；`gitea_repo_inventory_v1` 只能顯示 S4.5 認證匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation request、S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、owner response 收件包、intake preflight checks、outcome lanes 與覆蓋缺口，不得觸發 token collection 或 Gitea write。
+6. 只對 `approval_required_event_v1`、repo approval package、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1` 與 `source_control_workflow_secret_name_inventory_v1` 建 approval candidate / review lane / next-state display / runtime gate preparation / primary readiness display / rollback ADR display / workflow-secret name inventory gate / redacted export request display；`github_target_decision_v1` 只能顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、owner decision response templates、received_response_count=0、acceptance checks 與 rejection rules，不得觸發 repo creation、visibility change、refs sync 或 primary switch；`source_control_workflow_secret_name_inventory_v1` 只能顯示 S4.12 owner response request packet、template status ledger、audit event templates、owner response templates、received_response_count=0、acceptance checks 與 rejection rules，不得觸發 secret collection、workflow 修改或 runner 啟用；`gitea_repo_inventory_v1` 只能顯示 S4.5 認證匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation request、S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、owner response 收件包、intake preflight checks、outcome lanes 與覆蓋缺口，不得觸發 token collection 或 Gitea write。
 7. 不新增執行按鈕，不做 runtime enforcement。

 ## 3. 永久禁止
--- a/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md
+++ b/docs/security/SECURITY-SUPPLY-CHAIN-PROGRESS.md
@@ -27,7 +27,7 @@ python3 scripts/security/security-mirror-progress-guard.py

 ### 0.2 Headline 58% 不代表停滯

-近期 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks，以及 S4.12 request packet / template status ledger 都是有效進展，但它們是 framework detail，不是 owner response、runtime gate 或 GitHub primary readiness。因此 headline 仍維持 58%，避免把只讀框架誤算成已落地執行。
+近期 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks，以及 S4.12 request packet / template status ledger / audit event templates 都是有效進展，但它們是 framework detail，不是 owner response、runtime gate 或 GitHub primary readiness。因此 headline 仍維持 58%，避免把只讀框架誤算成已落地執行。

 | 最近完成 | 目前狀態 | headline delta |
 |----------|----------|----------------|
@@ -45,6 +45,7 @@ python3 scripts/security/security-mirror-progress-guard.py
 | S4.11 intake preflight checks | 已完成草案，只分類可審、補證、隔離、拒收或等待 | 0 |
 | S4.12 request packet | 已完成草案，只顯示 owner 要回覆哪 5 類 workflow / secret 名稱問題 | 0 |
 | S4.12 template status ledger | 已完成草案，5 類 workflow / secret 名稱 responses 仍 waiting owner response | 0 |
+| S4.12 audit event templates | 已完成草案，`emitted_event_count=0`，只定義脫敏 metadata | 0 |

 headline 要再往上，需要 S4.9 / S4.10 / S4.11 / S4.12 任一 owner response 收到並通過脫敏驗收，或人工批准後出現 active runtime gate、redacted payload ingestion、GitHub primary readiness 這類落地 evidence。

@@ -81,7 +82,7 @@ headline 要再往上，需要 S4.9 / S4.10 / S4.11 / S4.12 任一 owner respons
 | S4.1 Workflow / Secret 名稱 inventory 契約 | 完成草案 | `source_control_workflow_secret_name_inventory_v1` 已建立；8 個 candidate repos、7 個 in-scope repos 尚缺實際 inventory、0 個 complete、禁止收集 secret value | AwoooP 可顯示 workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱缺口，不可修改 workflow 或 secret |
 | S4.2 Workflow / Secret 名稱 local evidence | 完成草案 | 已建立 local read-only collector 與 snapshot；7 個 local repos visible、4 個 local evidence repos、31 個 workflow files、43 個 referenced secret names、secret value detected=false | 補 webhook / deploy key / branch protection / repository secret parity 的 redacted evidence；仍不可切 primary |
 | S4.3 Workflow / Secret 名稱 redacted export request | 完成草案 | 已建立 export request schema / snapshot / 人讀版；7 個 in-scope repos、5 類 export lanes：webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；write token allowed=false | repo owner 或未來只讀 API 依 request 補 redacted export；仍不可收 secret value、不可修改 GitHub/Gitea |
-| S4.12 Workflow / Secret Name Owner Response 收件包 | 完成草案 | 已建立 owner response schema / snapshot / 人讀版；1 個 owner response request packet、5 個 template statuses、5 個 response templates、8 個 acceptance checks、10 個 rejection rules、candidate repos 8、in-scope repos 7、received response 0、accepted 0、execution authorized=false | owner 依 request packet、template status ledger 與模板回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；response 通過只更新 read-only inventory / export request / readiness wording，不代表收 secret value、改 workflow、啟用 runner 或 primary approval |
+| S4.12 Workflow / Secret Name Owner Response 收件包 | 完成草案 | 已建立 owner response schema / snapshot / 人讀版；1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 response templates、8 個 acceptance checks、10 個 rejection rules、candidate repos 8、in-scope repos 7、received response 0、accepted 0、audit events emitted 0、execution authorized=false | owner 依 request packet、template status ledger、audit event templates 與模板回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity；response 通過只更新 read-only inventory / export request / readiness wording，不代表收 secret value、改 workflow、啟用 runner 或 primary approval |
 | S4.13 Source Control Owner Response Validation Rollup | 完成草案 | 已建立 validation rollup schema / snapshot / 人讀版；彙整 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets、4 條 missing response lanes、4 步 owner response collection order、next collection candidate、22 個 response templates、10 個 cross-packet checks、40 個 rejection rules、received / accepted / rejected response 皆為 0、execution authorized=false；latest local validation 為 `SOURCE_CONTROL_OWNER_RESPONSE_GUARD_OK` | AwoooP 可顯示四包 owner response 驗收總覽、缺口摘要、建議收件順序、下一個建議收件項目與 quarantine rules；rollup 不代表 approval、runtime gate、repo / refs / workflow / secret / runner 執行授權或 primary approval |
 | S4.4 GitHub Primary rollback ADR | 完成草案 | 已建立 rollback ADR schema / snapshot / 人讀版；7 個 in-scope rollback drafts、0 owner approved、0 dry-run completed、0 active cutover | repo owner 審查 rollback owner、validation window 與 triggers；仍不可切 primary 或執行 rollback |
 | S4.5 Gitea 認證清冊匯出請求 | 完成草案 | 已建立匯出請求 schema / snapshot / 人讀版；目前未認證公開範圍 repo 2 個、本機可見 Gitea unique repo 4 個、覆蓋缺口 2 個、匯出來源選項 2 類；允許收集 token value=false | repo owner 依只讀 token API 或已脫敏管理匯出補私有 / 內部全量 repo list；仍不可保存 token、不可 write Gitea、不可 refs sync |
@@ -207,10 +208,10 @@ headline 要再往上，需要 S4.9 / S4.10 / S4.11 / S4.12 任一 owner respons
 1. 先依 S4.9 `GITEA-INVENTORY-OWNER-ATTESTATION-RESPONSE.md` 收到並驗收 S4.7 `GITEA-INVENTORY-COVERAGE-ATTESTATION.md` 的 owner response；S4.8 已把這件事接到既有 approval queue / gate / review packet / follow-up runtime gate。之後再依 S4.5 `GITEA-AUTHENTICATED-INVENTORY-EXPORT-REQUEST.md` 取得 Gitea 認證清冊；收到 payload 後依 S4.6 `GITEA-AUTHENTICATED-INVENTORY-IMPORT-ACCEPTANCE.md` 驗收 / 拒收 / 隔離。目前未認證公開範圍 2 個、本機可見 Gitea unique 4 個、覆蓋缺口 2 個、attestation items 5 個、owner response 0 筆；只能用只讀 token API 或已脫敏管理匯出補私有 / 內部 server-side 全量 repo list，不保存 token value。
 2. 依 S4.10 `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 與 `SOURCE-CONTROL-APPROVAL-BOARD.md` 對 7 個 `approval_required=true` 的 GitHub target 做 owner / visibility / canonical response；目前 response 0 筆、accepted 0 筆，通過後也只更新 read-only decision table / approval package / readiness gate，不代表 repo creation、visibility change、refs sync 或 primary approval。
 3. 依 S4.11 `SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md` request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 `SOURCE-CONTROL-REF-TRUTH-CLASSIFICATION.md` 對 `awoooi`、`clawbot-v5`、`wooo-aiops` 做單 repo / 單 ref owner response 驗收；audit event templates 目前 0 emitted，redaction examples 只示範安全 metadata shape，collection checks 只維持 request / received / accepted 分離，preflight 只分類可審、補證、隔離、拒收或等待，response 通過也只更新 read-only classification / reconcile / readiness wording，仍不得 push/delete refs 或 force push。
-4. 依 S4.12 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` request packet / template status ledger 與 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md` 對 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 做 owner response 驗收；request packet 只顯示要回覆欄位與拒收 payload，template status ledger 只顯示 waiting，不代表已送出或已收到，response 通過也只更新 read-only inventory / export request / readiness wording，仍不得收 secret value、改 workflow 或啟用 runner。
+4. 依 S4.12 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` request packet / template status ledger / audit event templates 與 `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md` 對 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 做 owner response 驗收；request packet 只顯示要回覆欄位與拒收 payload，template status ledger 只顯示 waiting，audit event templates 只定義 0 emitted 的脫敏 metadata，不代表已送出、已收到或 production ingestion，response 通過也只更新 read-only inventory / export request / readiness wording，仍不得收 secret value、改 workflow 或啟用 runner。
 5. 依 S4.13 `SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md` 集中檢查 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets；rollup 通過也只更新 read-only wording，不代表 approval 或 execution authorization。
 6. 對 `ewoooc` / `momo-pro-system` 完成 server-side canonical 判定。
 7. 依 `KALI-SCAN-SCOPE-APPROVAL-PACKAGE.md` 取得 safe crawl、credentialed scan、runtime ingestion、full-upgrade / reboot 等 gate 的人工批准；不得直接接 `/execute`。
-8. AwoooP 主線先讀 `security_mirror_readiness_v1`、`security_mirror_intake_plan_v1`、`security_mirror_event_v1`、`security_mirror_route_v1`、`security_mirror_acceptance_v1`、`security_mirror_quarantine_v1`、`security_mirror_dry_run_v1`、`security_mirror_status_rollup_v1`、S4.13 `source_control_owner_response_validation_rollup_v1`、`security_approval_gate_v1`、`security_approval_decision_record_v1`、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1` 與 `source_control_workflow_secret_name_inventory_v1`，只建立 mirror-only / read-only policy 入口，不新增執行按鈕；其中 Gitea inventory 需同時顯示 S4.5 認證清冊匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation 與 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / 收件包，GitHub target 決策需同時顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 owner decision response templates，refs truth 需同時顯示 S4.11 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 templates，workflow / secret inventory 需同時顯示 S4.3 redacted export request、S4.12 owner response request packet、template status ledger 與 5 個 owner response templates，primary readiness 需同時顯示 S4.4 rollback ADR 草案。
+8. AwoooP 主線先讀 `security_mirror_readiness_v1`、`security_mirror_intake_plan_v1`、`security_mirror_event_v1`、`security_mirror_route_v1`、`security_mirror_acceptance_v1`、`security_mirror_quarantine_v1`、`security_mirror_dry_run_v1`、`security_mirror_status_rollup_v1`、S4.13 `source_control_owner_response_validation_rollup_v1`、`security_approval_gate_v1`、`security_approval_decision_record_v1`、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1` 與 `source_control_workflow_secret_name_inventory_v1`，只建立 mirror-only / read-only policy 入口，不新增執行按鈕；其中 Gitea inventory 需同時顯示 S4.5 認證清冊匯出請求、S4.6 匯入驗收契約、S4.7 owner coverage attestation 與 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / 收件包，GitHub target 決策需同時顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 owner decision response templates，refs truth 需同時顯示 S4.11 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與 templates，workflow / secret inventory 需同時顯示 S4.3 redacted export request、S4.12 owner response request packet、template status ledger、audit event templates 與 5 個 owner response templates，primary readiness 需同時顯示 S4.4 rollback ADR 草案。
 9. AwoooP 主線消費 `security_rollout_policy_v1` 時，只做 read-only policy，不做 runtime blocking。
-10. AwoooP 主線再讀 `security_approval_queue_v1`、`security_approval_gate_v1`、`security_approval_decision_record_v1`、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1`、`source_control_workflow_secret_name_inventory_v1` 與 `security_supply_chain_contract_manifest_v1`，顯示 review order、批准範圍、審查封包、決策紀錄、決策後狀態、後續 runtime gate 準備條件、Gitea inventory 覆蓋缺口、S4.5 認證匯出請求、S4.6 匯入驗收 / 隔離規則、S4.7 owner attestation items、S4.9 owner response request packet、S4.9 owner response template status ledger、S4.9 owner response audit event templates、S4.9 owner response redaction examples、S4.9 owner response display sections、S4.9 owner response collection checks、S4.9 owner response templates、S4.10 GitHub target owner response request packet、S4.10 GitHub target owner response template status ledger、S4.10 GitHub target owner response audit event templates、S4.10 GitHub target owner response redaction examples、S4.10 GitHub target owner response collection checks、S4.10 GitHub target owner response intake preflight checks、S4.10 GitHub target owner response templates、S4.11 refs truth owner response request packet、S4.11 refs truth owner response template status ledger、S4.11 refs truth owner response audit event templates、S4.11 refs truth owner response redaction examples、S4.11 refs truth owner response collection checks、S4.11 refs truth owner response intake preflight checks、S4.11 refs truth owner response templates、S4.12 workflow / secret 名稱 owner response request packet、S4.12 workflow / secret 名稱 owner response template status ledger、S4.12 workflow / secret 名稱 owner response templates、S4.13 owner response validation rollup、GitHub primary readiness blockers、rollback ADR 草案、workflow / secret 名稱 inventory 缺口、redacted export request 與 blocked reason，不新增 execution router。
+10. AwoooP 主線再讀 `security_approval_queue_v1`、`security_approval_gate_v1`、`security_approval_decision_record_v1`、`security_approval_review_packet_v1`、`security_approval_state_transition_v1`、`security_followup_runtime_gate_v1`、`source_control_primary_readiness_gate_v1`、`source_control_primary_rollback_adr_v1`、`source_control_workflow_secret_name_inventory_v1` 與 `security_supply_chain_contract_manifest_v1`，顯示 review order、批准範圍、審查封包、決策紀錄、決策後狀態、後續 runtime gate 準備條件、Gitea inventory 覆蓋缺口、S4.5 認證匯出請求、S4.6 匯入驗收 / 隔離規則、S4.7 owner attestation items、S4.9 owner response request packet、S4.9 owner response template status ledger、S4.9 owner response audit event templates、S4.9 owner response redaction examples、S4.9 owner response display sections、S4.9 owner response collection checks、S4.9 owner response templates、S4.10 GitHub target owner response request packet、S4.10 GitHub target owner response template status ledger、S4.10 GitHub target owner response audit event templates、S4.10 GitHub target owner response redaction examples、S4.10 GitHub target owner response collection checks、S4.10 GitHub target owner response intake preflight checks、S4.10 GitHub target owner response templates、S4.11 refs truth owner response request packet、S4.11 refs truth owner response template status ledger、S4.11 refs truth owner response audit event templates、S4.11 refs truth owner response redaction examples、S4.11 refs truth owner response collection checks、S4.11 refs truth owner response intake preflight checks、S4.11 refs truth owner response templates、S4.12 workflow / secret 名稱 owner response request packet、S4.12 workflow / secret 名稱 owner response template status ledger、S4.12 workflow / secret 名稱 owner response audit event templates、S4.12 workflow / secret 名稱 owner response templates、S4.13 owner response validation rollup、GitHub primary readiness blockers、rollback ADR 草案、workflow / secret 名稱 inventory 缺口、redacted export request 與 blocked reason，不新增 execution router。
--- a/docs/security/SOURCE-CONTROL-MIGRATION-MATRIX.md
+++ b/docs/security/SOURCE-CONTROL-MIGRATION-MATRIX.md
@@ -124,7 +124,7 @@ Repo-by-repo approval package 已建立，7 個 approval-required targets 皆為

 Ref truth classification 已建立，將 `awoooi`、`clawbot-v5`、`wooo-aiops` 的 141 個 refs 差異拆成 review lane。`main` / `dev` 屬真相來源判定，`drift/adopt-*` 先列 deprecated candidate，release / UAT tags 先列保留判定；S4.11 已補 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，5 個 templates、received / accepted response 皆為 0、audit events emitted 仍為 0。不得把分類結果、request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 直接執行成同步、刪除、force push 或 primary switch。

-Workflow / secret name owner response 已建立，S4.12 補 5 個 templates，對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；received / accepted response 皆為 0。不得把 response packet 當成 secret value collection、workflow modification、GitHub hosted runner enablement 或 primary approval。
+Workflow / secret name owner response 已建立，S4.12 補 1 個 request packet、5 個 template statuses、3 個 audit event templates 與 5 個 templates，對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；received / accepted response 皆為 0、audit events emitted 仍為 0。不得把 request packet、template status ledger、audit event templates 或 response packet 當成 secret value collection、workflow modification、GitHub hosted runner enablement 或 primary approval。

 Owner response validation rollup 已建立，S4.13 彙整 S4.9 / S4.10 / S4.11 / S4.12 四包 response packets，22 個 templates、10 個 cross-packet checks，received / accepted response 皆為 0。不得把 rollup 當成 approval、runtime gate 或 execution authorization。

@@ -158,7 +158,7 @@ Ref truth classification 補充：完整 review lane 見 `docs/security/SOURCE-C
 1. 先批准 Gitea read-only inventory package，再用只讀 token 或管理匯出補齊 Gitea server repo list。
 2. 依 GitHub target repo-by-repo approval package 處理 7 個 approval-required target。
 3. 依 S4.11 ref truth owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / 收件包與 classification 釐清 `wooo/awoooi`、`wooo/clawbot-v5`、`wooo/wooo-aiops` 的雙端分歧來源；仍不得 push/delete refs。
-4. 依 S4.12 workflow / secret name owner response 收件包補 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted disposition；仍不得收 secret value、改 workflow 或啟用 hosted runner。
+4. 依 S4.12 workflow / secret name owner response request packet / template status ledger / audit event templates / 收件包補 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted disposition；仍不得收 secret value、改 workflow 或啟用 hosted runner。
 5. 依 S4.13 owner response validation rollup 集中檢查 S4.9-S4.12 四包 response validation；仍不得把 rollup 當 approval 或 execution authorization。
 6. 釐清 `wooo/ewoooc`、`root/momo-pro-system`、`momo-pro-system`、`momo_pro_system` 的 canonical 關係。
 7. 釐清 `bitan-pharmacy`、`tsenyang-website` 是否仍 active，並決定 GitHub owner / visibility。
--- a/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md
+++ b/docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md
@@ -58,7 +58,7 @@ S4.13 不新增第 36 個主 contract，不新增 approval item，不啟用 runt
 | S4.9 Gitea owner attestation response | `GITEA-INVENTORY-OWNER-ATTESTATION-RESPONSE.md` | 5 | 等待 response |
 | S4.10 GitHub target owner decision response | `GITHUB-TARGET-OWNER-DECISION-RESPONSE.md` | 7 | 等待 response |
 | S4.11 refs truth owner response | `SOURCE-CONTROL-REF-TRUTH-OWNER-RESPONSE.md` | 5 | 等待 response |
-| S4.12 workflow / secret name owner response | `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` | 5 | request packet / template status ledger 已定義，等待 response |
+| S4.12 workflow / secret name owner response | `SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md` | 5 | request packet / template status ledger / audit event templates 已定義，等待 response |

 ## 2.1 AwoooP 可顯示的缺口摘要

@@ -67,7 +67,7 @@ S4.13 不新增第 36 個主 contract，不新增 approval item，不啟用 runt
 | S4.9 Gitea owner attestation | 5 個 response templates 尚未收到 | Owner 回覆 5 個 Gitea coverage attestation items，只引用脫敏 evidence refs | 不收 token value、不寫 Gitea、不 sync refs、不切 primary |
 | S4.10 GitHub target decision | 7 個 response templates 尚未收到 | Owner 依 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 回覆 7 個 GitHub target 的 owner / visibility / canonical disposition | 不建 repo、不改 visibility、不 sync refs、不切 primary |
 | S4.11 refs truth | 5 個 response templates 尚未收到 | Owner 依 S4.11 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 回覆 refs truth、deprecated drift、release tags 與 GitHub-only refs disposition | 不 fetch / push / delete refs、不 force push、不切 primary |
-| S4.12 workflow / secret name | 1 個 request packet 已定義、5 個 template statuses 仍 waiting、5 個 response templates 尚未收到 | Owner 依 request packet 回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、secret name parity 的脫敏狀態 | 不收 secret value、不改 workflow、不啟用 runner、不切 primary |
+| S4.12 workflow / secret name | 1 個 request packet 已定義、5 個 template statuses 仍 waiting、3 個 audit event templates 仍 0 emitted、5 個 response templates 尚未收到 | Owner 依 request packet 與 audit event templates 回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、secret name parity 的脫敏狀態 | 不收 secret value、不改 workflow、不啟用 runner、不切 primary |

 ## 2.2 建議收件順序

--- a/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md
+++ b/docs/security/SOURCE-CONTROL-PRIMARY-READINESS-GATE.md
@@ -39,7 +39,7 @@
 |------|----------|------|
 | Gitea authenticated inventory | blocked | private/internal 全量 repo list 尚未完成；S4.9 owner response request packet、template status ledger、audit event templates、redaction examples、display sections 與 collection checks 已可顯示，但 S4.7 owner coverage attestation response 仍未收到，audit events emitted 仍為 0；S4.13 已集中顯示四包 owner response validation，但 total accepted response 仍為 0 |
 | refs truth / branch-tag parity | blocked | 3 個 mapped repos 仍有 refs drift；S4.11 已補 refs truth owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，received / accepted response 皆為 0、audit events emitted 仍為 0 |
-| workflow / runner / secret name parity | missing evidence | S4.1 已建立 inventory 契約；S4.12 已補 owner response 收件包，received / accepted response 皆為 0；尚未有實際 redacted workflow、webhook、runner、secret 名稱 snapshot |
+| workflow / runner / secret name parity | missing evidence | S4.1 已建立 inventory 契約；S4.12 已補 owner response request packet、template status ledger、audit event templates 與收件包，received / accepted response 皆為 0、audit events emitted 仍為 0；尚未有實際 redacted workflow、webhook、runner、secret 名稱 snapshot |
 | owner / visibility / canonical | pending review | 7 個 in-scope targets 仍需人工決策；S4.10 已補 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，received / accepted response 皆為 0 |
 | rollback ADR | pending review | S4.4 已建立 rollback ADR 草案；7 個 in-scope repos 仍需 owner approval、dry-run 與 validation window |

@@ -48,11 +48,11 @@
 1. 顯示每個 repo 的 readiness state、blockers 與 evidence refs。
 2. 顯示 `primary_ready_count=0`。
 3. 將 7 個 in-scope repos 維持在 approval / review lane。
-4. 顯示哪些 evidence 仍缺：Gitea authenticated inventory、S4.7 owner coverage attestation、S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / owner response、S4.10 GitHub target owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response、S4.11 refs truth owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response、S4.12 workflow / secret name owner response、S4.13 validation rollup、workflow/runner/secret name inventory、rollback ADR。
+4. 顯示哪些 evidence 仍缺：Gitea authenticated inventory、S4.7 owner coverage attestation、S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / owner response、S4.10 GitHub target owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response、S4.11 refs truth owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / owner response、S4.12 workflow / secret name owner response request packet / template status ledger / audit event templates / owner response、S4.13 validation rollup、workflow/runner/secret name inventory、rollback ADR。
 5. 連到 S4.10 `github_target_owner_decision_response_v1` 顯示 1 個 owner response request packet、7 個 owner response template statuses、3 個 owner response audit event templates、5 個 owner response redaction examples、6 個 owner response collection checks、6 個 intake preflight checks、7 個 owner decision response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。
 6. 連到 S4.11 `source_control_ref_truth_owner_response_v1` 顯示 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks、5 個 refs owner response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0、audit events emitted 仍為 0。
 7. 連到 `source_control_workflow_secret_name_inventory_v1` 顯示 8 個 candidate repos 的 inventory lane 缺口與 S4.2 local evidence；只保存 secret 名稱與 owner，不保存 value。
-8. 連到 S4.12 `source_control_workflow_secret_name_owner_response_v1` 顯示 5 個 owner response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0。
+8. 連到 S4.12 `source_control_workflow_secret_name_owner_response_v1` 顯示 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 owner response templates、8 個 acceptance checks、10 個 rejection rules，且 received / accepted response 皆為 0、audit events emitted 仍為 0。
 9. 連到 S4.13 `source_control_owner_response_validation_rollup_v1` 顯示四包 owner response validation 狀態：22 個 templates、10 個 cross-packet checks、received / accepted / rejected response 皆為 0。
 10. 連到 `source_control_primary_rollback_adr_v1` 顯示 7 個 in-scope repos 的 rollback owner、trigger 與 validation window 草案。
 11. 把狀態寫入 Audit evidence 與 Operator Console。
@@ -71,6 +71,6 @@

 S4.0 只是把「切換前一定要看見什麼」先定義清楚。

-S4.4 已補上 rollback ADR 草案，但它只是 owner review 的資料包，不是切換批准。S4.7 已補上 Gitea coverage owner attestation，S4.9 已補上 Gitea owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、收件包、preflight 與 outcome lanes，S4.10 已補上 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，S4.11 已補上 refs truth owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，S4.12 已補上 workflow / secret 名稱 owner response 收件包，S4.13 已補上四包 owner response validation rollup；它們只是 scope decision、response 收件提示、metadata audit template、脫敏範例、只讀收件檢查、只讀 preflight、只讀顯示順序與驗收框架，不是 audit production ingestion、migration approval、repo creation approval、visibility change approval、refs sync approval、delete approval、force-push approval、secret value collection approval、workflow modification approval 或 primary approval。`owner_approved_count=0`、`dry_run_completed_count=0`、`active_cutover_count=0`。
+S4.4 已補上 rollback ADR 草案，但它只是 owner review 的資料包，不是切換批准。S4.7 已補上 Gitea coverage owner attestation，S4.9 已補上 Gitea owner response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks、收件包、preflight 與 outcome lanes，S4.10 已補上 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，S4.11 已補上 refs truth owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包，S4.12 已補上 workflow / secret 名稱 owner response request packet、template status ledger、audit event templates 與收件包，S4.13 已補上四包 owner response validation rollup；它們只是 scope decision、response 收件提示、metadata audit template、脫敏範例、只讀收件檢查、只讀 preflight、只讀顯示順序與驗收框架，不是 audit production ingestion、migration approval、repo creation approval、visibility change approval、refs sync approval、delete approval、force-push approval、secret value collection approval、workflow modification approval 或 primary approval。`owner_approved_count=0`、`dry_run_completed_count=0`、`active_cutover_count=0`。

 這讓長期回到 GitHub 的方向可以繼續往前，但仍維持低摩擦：目前只 mirror、只顯示、只留痕，不執行。
--- a/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md
+++ b/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md
@@ -15,7 +15,7 @@

 S4.3 把 S4.2 還缺的控制面 evidence 拆成可交接的 redacted export request。

-這不是 API 執行、不是 GitHub primary cutover、也不是 workflow / secret 修改。它只是告訴 repo owner 或未來只讀匯出工具：每個 repo 要補哪些欄位、哪些欄位可以保存、哪些敏感值必須拒收。S4.12 已補 owner response request packet、template status ledger 與收件包，讓請求、等待狀態與回覆可審、可驗收、可拒收，但仍不授權任何變更。
+這不是 API 執行、不是 GitHub primary cutover、也不是 workflow / secret 修改。它只是告訴 repo owner 或未來只讀匯出工具：每個 repo 要補哪些欄位、哪些欄位可以保存、哪些敏感值必須拒收。S4.12 已補 owner response request packet、template status ledger、audit event templates 與收件包，讓請求、等待狀態、0 emitted 脫敏 audit metadata 與回覆可審、可驗收、可拒收，但仍不授權任何變更。

 ## 1. 摘要

@@ -27,6 +27,7 @@ S4.3 把 S4.2 還缺的控制面 evidence 拆成可交接的 redacted export req
 | Export lanes | 5 |
 | S4.12 request packet | 1 |
 | S4.12 template statuses | 5 |
+| S4.12 audit event templates | 3 |
 | S4.12 response templates | 5 |
 | S4.12 received / accepted / rejected | `0 / 0 / 0` |
 | Webhook export request repos | 2 |
@@ -68,7 +69,7 @@ S4.3 把 S4.2 還缺的控制面 evidence 拆成可交接的 redacted export req
 3. 顯示 GitHub hosted runner 可能造成額度消耗的 review lane。
 4. 把完成的 redacted export 作為 Audit evidence 等待人工審查。
 5. 若 payload 含敏感值，送進 mirror quarantine。
-6. 顯示 S4.12 owner response request packet、template status ledger、templates、acceptance checks 與 rejection rules。
+6. 顯示 S4.12 owner response request packet、template status ledger、audit event templates、templates、acceptance checks 與 rejection rules。

 ## 5. AwoooP 不可做

@@ -82,6 +83,6 @@ S4.3 把 S4.2 還缺的控制面 evidence 拆成可交接的 redacted export req

 S4.1 建立 inventory gate，S4.2 補本機 workflow / CODEOWNERS / referenced secret name evidence，S4.3 補「下一步匯出請求包」。

-S4.12 補「owner response request packet、template status ledger 與收件包」，固定 5 類 export lanes 的請求欄位、等待狀態、回覆欄位與拒收規則，避免後續誤收 secret value、誤用 write token、誤啟 GitHub hosted runner 或誤改 workflow。
+S4.12 補「owner response request packet、template status ledger、audit event templates 與收件包」，固定 5 類 export lanes 的請求欄位、等待狀態、0 emitted 脫敏 audit metadata、回覆欄位與拒收規則，避免後續誤收 secret value、誤用 write token、誤啟 GitHub hosted runner 或誤改 workflow。

 這仍然是低摩擦框架期：先把資料責任、欄位邊界與拒收規則定清楚，避免後續真的接 owner export 或只讀 API 時誤收秘密值、誤用 write token，或誤把資料補齊當成主控切換批准。
--- a/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-INVENTORY.md
+++ b/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-INVENTORY.md
@@ -24,7 +24,7 @@ S4.2 已補本機可見 evidence：4 個 repos 有 workflow / CODEOWNERS evidenc

 S4.3 已補 redacted export request package：7 個 in-scope repos 需要 owner / read-only export，5 類 export lanes 包含 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；所有 export 都禁止 secret value 與 write token。

-S4.12 已補 owner response request packet、template status ledger 與收件包：1 個 request packet、5 個 template statuses 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；目前 received / accepted response 皆為 0。response 通過也只更新 read-only evidence，不代表修改 workflow、secret、runner、deploy key 或 branch protection。
+S4.12 已補 owner response request packet、template status ledger、audit event templates 與收件包：1 個 request packet、5 個 template statuses、3 個 audit event templates 與 5 個 response templates 對應 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret name parity；目前 received / accepted response 皆為 0、audit events emitted 仍為 0。response 通過也只更新 read-only evidence，不代表修改 workflow、secret、runner、deploy key 或 branch protection。

 ## 1. 目前狀態

@@ -43,6 +43,7 @@ S4.12 已補 owner response request packet、template status ledger 與收件包
 | Redacted export lanes | 5 |
 | S4.12 request packet | 1 |
 | S4.12 template statuses | 5 |
+| S4.12 audit event templates | 3 |
 | S4.12 response templates | 5 |
 | S4.12 received / accepted / rejected | `0 / 0 / 0` |

@@ -67,7 +68,7 @@ S4.12 已補 owner response request packet、template status ledger 與收件包
 5. 將失敗或含敏感值 payload 交給 mirror quarantine。
 6. 顯示 S4.2 本機 evidence 與仍缺的 API / export lanes。
 7. 顯示 S4.3 export request 的欄位清單、拒收欄位與 acceptance gate。
-8. 顯示 S4.12 owner response request packet、template status ledger、templates、acceptance checks 與 rejection rules。
+8. 顯示 S4.12 owner response request packet、template status ledger、audit event templates、templates、acceptance checks 與 rejection rules。

 ## 4. AwoooP 不可做

@@ -87,6 +88,6 @@ S4.2 讓本機可見 workflow / CODEOWNERS / referenced secret names 先形成 p

 S4.3 讓後續 webhook、runner、deploy key、branch protection / CODEOWNERS 與 repository secret parity 的 owner / read-only export 有明確的欄位、拒收規則與驗收 gate。

-S4.12 讓 owner response request、template status 與 response 有固定收件格式與拒收規則，避免 GitHub hosted runner 額度風險、secret value、write token 或未脫敏 payload 被誤接進 AwoooP。
+S4.12 讓 owner response request、template status、audit event templates 與 response 有固定收件格式與拒收規則，避免 GitHub hosted runner 額度風險、secret value、write token 或未脫敏 payload 被誤接進 AwoooP。

 這仍是低摩擦框架期：只定義欄位、只顯示缺口、只留痕，不碰任何實際 secret 或發版流程。後續即使取得 redacted export，也只代表 evidence 可 review，不代表 GitHub primary ready。
--- a/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md
+++ b/docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md
@@ -33,6 +33,7 @@ S4.12 不是 secret 搬移、不是 workflow 修改、不是 runner 啟用、不
 | local referenced secret names | 43 |
 | owner response request packet | 1 |
 | template status ledger | 5 |
+| audit event templates | 3 |
 | response templates | 5 |
 | 已收到 response | 0 |
 | 已接受 response | 0 |
@@ -72,6 +73,16 @@ Owner 回覆只能使用脫敏 metadata 或既有文件引用。不得貼 secret

 Template status ledger 只讓 AwoooP 逐項顯示哪一類 workflow / secret name response 還在等待 owner。`request_ready_not_sent` 不代表 request 已送出，`waiting_owner_response` 不代表 owner 已回覆，任何單項狀態也不代表 secret value collection、workflow 修改、webhook 修改、runner 啟用、deploy key 變更、branch protection 修改、repository secret 建立、refs sync 或 GitHub primary approval。

+## 1.3 Audit Event Templates
+
+| Template | 觸發點 | emitted |
+|----------|--------|---------|
+| `audit-workflow-secret-response-request-shown` | 顯示 S4.12 request packet | 0 |
+| `audit-workflow-secret-response-received-metadata` | 收到脫敏 owner response metadata pointer | 0 |
+| `audit-workflow-secret-response-outcome-classified` | 依 acceptance checks / rejection rules 分類 outcome | 0 |
+
+Audit event templates 只定義 AwoooP 未來可記錄的 workflow / secret name owner response 脫敏 metadata 欄位，全部維持 `template_only_not_emitted`、`emitted_event_count=0`、`stored_raw_payload_allowed=false`。它們不是 production ingestion，不代表 owner response 已收到，也不授權 secret value collection、workflow 修改、webhook 修改、runner 啟用、deploy key rotation、branch protection change、repository secret change、refs sync 或 GitHub primary。
+
 ## 2. Owner Response 必填欄位

 每筆 response 至少要能回答：
@@ -132,12 +143,13 @@ Template status ledger 只讓 AwoooP 逐項顯示哪一類 workflow / secret nam

 1. 顯示 1 個 owner response request packet。
 2. 顯示 5 個 template statuses，逐項維持 `waiting_owner_response`。
-3. 顯示 5 個 owner response templates。
-4. 顯示 8 個 acceptance checks 與 10 個 rejection rules。
-5. 顯示 GitHub hosted runner 額度風險 review lane，但不啟用 hosted runner。
-6. 在 owner response 到來後，只更新 read-only inventory、export request、primary readiness blocker wording 與 status rollup。
-7. 將不完整或可疑 response 放進 mirror quarantine。
-8. 持續顯示 `received_response_count=0`、`accepted_response_count=0`，直到真的收到脫敏 response。
+3. 顯示 3 個 audit event templates，全部維持 `template_only_not_emitted` 與 `emitted_event_count=0`。
+4. 顯示 5 個 owner response templates。
+5. 顯示 8 個 acceptance checks 與 10 個 rejection rules。
+6. 顯示 GitHub hosted runner 額度風險 review lane，但不啟用 hosted runner。
+7. 在 owner response 到來後，只更新 read-only inventory、export request、primary readiness blocker wording 與 status rollup。
+8. 將不完整或可疑 response 放進 mirror quarantine。
+9. 持續顯示 `received_response_count=0`、`accepted_response_count=0`，直到真的收到脫敏 response。

 ## 8. AwoooP 不可做

--- a/docs/security/security-approval-gate.snapshot.json
+++ b/docs/security/security-approval-gate.snapshot.json
@@ -140,7 +140,7 @@
      "decision_options": ["approve_scope", "reject", "defer", "request_more_evidence"],
      "allowed_after_approval": [
        "依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 驗收 owner decision response",
-        "依 S4.12 request packet / template status ledger 驗收 workflow / secret 名稱 owner response",
+        "依 S4.12 request packet / template status ledger / audit event templates 驗收 workflow / secret 名稱 owner response",
        "逐 repo 更新 owner/visibility/canonical decision",
        "更新 workflow / secret name parity read-only wording",
        "產生 draft reconcile plan 或 ADR",
@@ -150,7 +150,7 @@
        "建立 repo",
        "修改 visibility",
        "把 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo creation 或 visibility approval",
-        "把 S4.12 request packet、template status ledger 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
+        "把 S4.12 request packet、template status ledger、audit event templates 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
        "push refs",
        "delete refs",
        "切 GitHub primary"
--- a/docs/security/security-approval-queue.snapshot.json
+++ b/docs/security/security-approval-queue.snapshot.json
@@ -126,7 +126,7 @@
      "risk": "HIGH",
      "state": "pending_approval",
      "recommended_awooop_mode": "approve_required",
-      "requested_decision": "是否依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 逐 repo 收到並驗收 GitHub target、owner、visibility、canonical response，並依 S4.12 request packet / template status ledger 驗收 workflow / secret 名稱 owner response；此 bundle 不授權執行。",
+      "requested_decision": "是否依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 逐 repo 收到並驗收 GitHub target、owner、visibility、canonical response，並依 S4.12 request packet / template status ledger / audit event templates 驗收 workflow / secret 名稱 owner response；此 bundle 不授權執行。",
      "blocked_until_approved": true,
      "required_reviewers": [
        "migration-engineer",
@@ -144,7 +144,7 @@
      ],
      "allowed_after_approval": [
        "依 S4.10 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks 驗收 owner decision response",
-        "依 S4.12 request packet / template status ledger 驗收 workflow / secret 名稱 owner response",
+        "依 S4.12 request packet / template status ledger / audit event templates 驗收 workflow / secret 名稱 owner response",
        "逐 repo 更新 owner/visibility/canonical decision",
        "更新 workflow / secret name parity read-only wording",
        "產生 draft reconcile plan 或 ADR",
@@ -154,7 +154,7 @@
        "建立 repo",
        "修改 visibility",
        "把 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo creation 或 visibility approval",
-        "把 S4.12 request packet、template status ledger 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
+        "把 S4.12 request packet、template status ledger、audit event templates 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
        "push refs",
        "delete refs",
        "切 GitHub primary"
--- a/docs/security/security-approval-review-packet.snapshot.json
+++ b/docs/security/security-approval-review-packet.snapshot.json
@@ -176,7 +176,7 @@
      "allowed_pre_decision_actions": [
        "顯示 7 個 approval-required target",
        "顯示 S4.10 owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks、owner response templates、received_response_count=0 與 rejection rules",
-        "顯示 S4.12 workflow / secret 名稱 owner response request packet、template statuses、templates、received_response_count=0 與 rejection rules",
+        "顯示 S4.12 workflow / secret 名稱 owner response request packet、template statuses、audit event templates、templates、received_response_count=0 與 rejection rules",
        "要求 repo owner 補 owner/visibility/canonical 判定",
        "維持 refs action disabled"
      ],
@@ -188,7 +188,7 @@
        "建立 repo",
        "修改 visibility",
        "把 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當成 repo creation 或 visibility approval",
-        "把 S4.12 request packet、template status ledger 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
+        "把 S4.12 request packet、template status ledger、audit event templates 或 response packet 當成 secret value collection、workflow modification 或 runner enablement approval",
        "push refs",
        "delete refs",
        "切 GitHub primary"
--- a/docs/security/security-followup-runtime-gate.snapshot.json
+++ b/docs/security/security-followup-runtime-gate.snapshot.json
@@ -158,7 +158,7 @@
      "applies_after_decision": "approve_scope",
      "minimum_required_evidence": [
        "S4.10 owner response request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight checks / decision response 驗收結果：docs/security/github-target-owner-decision-response.snapshot.json",
-        "S4.12 workflow / secret 名稱 owner response request packet、template status ledger 與驗收結果：docs/security/source-control-workflow-secret-name-owner-response.snapshot.json",
+        "S4.12 workflow / secret 名稱 owner response request packet、template status ledger、audit event templates 與驗收結果：docs/security/source-control-workflow-secret-name-owner-response.snapshot.json",
        "repo owner / visibility / canonical decision",
        "GitHub target 是否已存在的最新 probe",
        "workflow parity checklist",
@@ -171,7 +171,7 @@
      ],
      "preflight_checks": [
        "確認 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 未被當成 repo creation、visibility change、refs sync 或 primary approval",
-        "確認 S4.12 request packet、template status ledger 或 response packet 未被當成 secret value collection、workflow modification、runner enablement 或 primary approval",
+        "確認 S4.12 request packet、template status ledger、audit event templates 或 response packet 未被當成 secret value collection、workflow modification、runner enablement 或 primary approval",
        "確認 not_found_or_private 不被當成可自動建立 repo",
        "確認 visibility change 仍未授權",
        "確認 refs action disabled",
--- a/docs/security/security-mirror-dry-run.snapshot.json
+++ b/docs/security/security-mirror-dry-run.snapshot.json
@@ -107,7 +107,7 @@
    },
    {
      "step_id": "CHECK_OWNER_RESPONSE_GUARD",
-      "expected_observation": "AwoooP dry-run 必須確認 S4.9 / S4.10 / S4.11 / S4.12 四包 owner response 仍為 waiting_owner_response，received / accepted 皆為 0，且 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / intake preflight / outcome lanes 只提示 owner，S4.10 owner response request packet 只提示 7 個 GitHub target 要回覆的 owner / visibility / canonical 欄位，S4.10 template status ledger 逐項顯示 waiting / request ready，S4.10 audit event templates 只定義 0 emitted 的脫敏 metadata，S4.10 redaction examples 只顯示可接受的脫敏 metadata shape，S4.10 collection checks 只維持 request / received / accepted 分離，S4.10 intake preflight checks 只分類可收、補證、隔離或拒收，S4.11 request packet 只提示 5 類 refs truth owner response 欄位，S4.11 template status ledger 逐項顯示 waiting / request ready，S4.11 audit event templates 只定義 0 emitted 的脫敏 metadata，S4.11 redaction examples 只顯示安全 metadata shape，S4.11 collection checks 只維持 request / received / accepted 分離，S4.11 intake preflight checks 只分類可審、補證、隔離、拒收或等待，S4.12 request packet 只提示 5 類 workflow / secret 名稱 owner response 欄位，S4.12 template status ledger 逐項顯示 waiting / request ready；不能把 request shown、template status、response received metadata、redaction example、collection check pass、preflight pass 或 outcome classified 當成 approval，不能解鎖 repo、refs、workflow、secret、runner、GitHub primary、audit production ingestion 或 runtime action。",
+      "expected_observation": "AwoooP dry-run 必須確認 S4.9 / S4.10 / S4.11 / S4.12 四包 owner response 仍為 waiting_owner_response，received / accepted 皆為 0，且 S4.9 owner response request packet / template status ledger / audit event templates / redaction examples / display sections / collection checks / intake preflight / outcome lanes 只提示 owner，S4.10 owner response request packet 只提示 7 個 GitHub target 要回覆的 owner / visibility / canonical 欄位，S4.10 template status ledger 逐項顯示 waiting / request ready，S4.10 audit event templates 只定義 0 emitted 的脫敏 metadata，S4.10 redaction examples 只顯示可接受的脫敏 metadata shape，S4.10 collection checks 只維持 request / received / accepted 分離，S4.10 intake preflight checks 只分類可收、補證、隔離或拒收，S4.11 request packet 只提示 5 類 refs truth owner response 欄位，S4.11 template status ledger 逐項顯示 waiting / request ready，S4.11 audit event templates 只定義 0 emitted 的脫敏 metadata，S4.11 redaction examples 只顯示安全 metadata shape，S4.11 collection checks 只維持 request / received / accepted 分離，S4.11 intake preflight checks 只分類可審、補證、隔離、拒收或等待，S4.12 request packet 只提示 5 類 workflow / secret 名稱 owner response 欄位，S4.12 template status ledger 逐項顯示 waiting / request ready，S4.12 audit event templates 只定義 0 emitted 的脫敏 metadata；不能把 request shown、template status、response received metadata、redaction example、collection check pass、preflight pass 或 outcome classified 當成 approval，不能解鎖 repo、refs、workflow、secret、runner、GitHub primary、audit production ingestion 或 runtime action。",
      "evidence_refs": [
        "docs/security/source-control-owner-response-validation-rollup.snapshot.json",
        "docs/security/SOURCE-CONTROL-OWNER-RESPONSE-VALIDATION-ROLLUP.md",
--- a/docs/security/security-mirror-readiness.snapshot.json
+++ b/docs/security/security-mirror-readiness.snapshot.json
@@ -395,7 +395,7 @@
        "docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-EXPORT-REQUEST.md",
        "docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md"
      ],
-      "notes": "可 mirror workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 缺口；S4.2 local evidence 有 4 個 repos、31 個 workflow files、43 個 referenced secret names；S4.3 export request 有 7 個 repos、5 類 export lanes；S4.12 owner response request packet 1 個、template statuses 5 個、templates 5 個、received_response_count=0；secret_value_collection_allowed=false。"
+      "notes": "可 mirror workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 缺口；S4.2 local evidence 有 4 個 repos、31 個 workflow files、43 個 referenced secret names；S4.3 export request 有 7 個 repos、5 類 export lanes；S4.12 owner response request packet 1 個、template statuses 5 個、audit event templates 3 個、templates 5 個、received_response_count=0、audit_events_emitted=0；secret_value_collection_allowed=false。"
    },
    {
      "contract": "local_repo_canonical_probe_v1",
--- a/docs/security/security-mirror-status-rollup.snapshot.json
+++ b/docs/security/security-mirror-status-rollup.snapshot.json
@@ -143,15 +143,15 @@
    {
      "phase_id": "S4_migration_execution",
      "state": "not_started",
-      "current_result": "GitHub primary 是長期方向；source_control_primary_readiness_gate_v1 已定義 8 個 candidate repos、7 個 in-scope blocked repos、0 個 primary ready；S4.1 已定義 workflow / secret 名稱 inventory 契約；S4.2 已補 local evidence；S4.3 已補 redacted export request；S4.4 已補 rollback ADR 草案；S4.5 已補 Gitea authenticated inventory export request；S4.6 已補 redacted import acceptance；S4.7 已補 owner coverage attestation request；S4.9 已補 Gitea owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response intake packet、6 個 intake preflight checks 與 5 個 outcome lanes；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與 intake packet；S4.11 已補 refs truth owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包；S4.12 已補 workflow / secret 名稱 owner response request packet、5 個 template statuses 與 intake packet；S4.13 已補四包 owner response validation rollup，彙整 22 個 templates、received=0、accepted=0，並標示 next_collection_candidate=S4.9，但 inventory status 仍 partial，S4.9/S4.11 audit events emitted 仍 0 筆，GitHub target / refs truth / workflow-secret response 仍 0 筆。",
-      "next_gate": "依 S4.13 先集中檢查四包 owner response validation 狀態，AwoooP 只顯示 next_collection_candidate=S4.9 Gitea owner attestation，依 S4.9 owner response request packet 要求 owner 回覆，並用 template status ledger / audit event templates / redaction examples / display sections / collection checks 維持 request / received / accepted 分離；再依 S4.9 收到並驗收 S4.7 Gitea owner response、依 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 7 個 GitHub target owner / visibility / canonical response、依 S4.11 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 5 個 refs truth owner response templates、依 S4.12 request packet 與 template status ledger 收到並驗收 5 個 workflow / secret 名稱 owner response templates、authenticated inventory payload 通過 S4.6 驗收、rollback ADR owner approval 與逐 repo 人工批准。"
+      "current_result": "GitHub primary 是長期方向；source_control_primary_readiness_gate_v1 已定義 8 個 candidate repos、7 個 in-scope blocked repos、0 個 primary ready；S4.1 已定義 workflow / secret 名稱 inventory 契約；S4.2 已補 local evidence；S4.3 已補 redacted export request；S4.4 已補 rollback ADR 草案；S4.5 已補 Gitea authenticated inventory export request；S4.6 已補 redacted import acceptance；S4.7 已補 owner coverage attestation request；S4.9 已補 Gitea owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、8 個 display sections、6 個 collection checks、owner response intake packet、6 個 intake preflight checks 與 5 個 outcome lanes；S4.10 已補 GitHub target owner decision response request packet、7 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與 intake packet；S4.11 已補 refs truth owner response request packet、5 個 template statuses、3 個 audit event templates、5 個 redaction examples、6 個 collection checks、6 個 intake preflight checks 與收件包；S4.12 已補 workflow / secret 名稱 owner response request packet、5 個 template statuses、3 個 audit event templates 與 intake packet；S4.13 已補四包 owner response validation rollup，彙整 22 個 templates、received=0、accepted=0，並標示 next_collection_candidate=S4.9，但 inventory status 仍 partial，S4.9/S4.11/S4.12 audit events emitted 仍 0 筆，GitHub target / refs truth / workflow-secret response 仍 0 筆。",
+      "next_gate": "依 S4.13 先集中檢查四包 owner response validation 狀態，AwoooP 只顯示 next_collection_candidate=S4.9 Gitea owner attestation，依 S4.9 owner response request packet 要求 owner 回覆，並用 template status ledger / audit event templates / redaction examples / display sections / collection checks 維持 request / received / accepted 分離；再依 S4.9 收到並驗收 S4.7 Gitea owner response、依 S4.10 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 7 個 GitHub target owner / visibility / canonical response、依 S4.11 request packet、template status ledger、audit event templates、redaction examples、collection checks 與 intake preflight checks 收到並驗收 5 個 refs truth owner response templates、依 S4.12 request packet、template status ledger 與 audit event templates 收到並驗收 5 個 workflow / secret 名稱 owner response templates、authenticated inventory payload 通過 S4.6 驗收、rollback ADR owner approval 與逐 repo 人工批准。"
    }
  ],
  "progress_display_policy": {
    "headline_percent": 58,
    "headline_status": "holding_until_owner_response_or_runtime_gate",
    "why_headline_is_holding": [
-      "最近完成的是 S4.10 owner response request / status / audit / redaction / collection checks / intake preflight 與 S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight 的框架細節，改善可見性與收件安全，但 owner response received / accepted 仍為 0。",
+      "最近完成的是 S4.10 owner response request / status / audit / redaction / collection checks / intake preflight、S4.11 request packet / template status ledger / audit event templates / redaction examples / collection checks / intake preflight，以及 S4.12 request packet / template status ledger / audit event templates 的框架細節，改善可見性與收件安全，但 owner response received / accepted 仍為 0。",
      "overall_percent 只在 owner response、redacted payload ingestion、active runtime gate、GitHub primary readiness 或 AwoooP production ingestion 這些高層 gate 有實質變化時調整。",
      "維持 58% 是為了避免把 read-only scaffold 誤算成 runtime enforcement、Kali scan、repo migration 或 GitHub primary cutover。"
    ],
@@ -335,6 +335,18 @@
      "runtime_delta": false,
      "execution_authorized": false,
      "not_authorization": true
+    },
+    {
+      "delta_id": "s4_12_workflow_secret_name_owner_response_audit_event_templates",
+      "display_order": 15,
+      "completed_stage": "S4.12 workflow / secret 名稱 owner response audit event templates",
+      "progress_axis": "framework_detail",
+      "headline_percent_delta": 0,
+      "framework_delta_visible": true,
+      "why_headline_unchanged": "audit event templates 仍為 template_only_not_emitted，emitted_event_count=0，尚未啟用 production ingestion，也不代表 secret value collection、workflow 修改、runner 啟用或 primary 授權。",
+      "runtime_delta": false,
+      "execution_authorized": false,
+      "not_authorization": true
    }
  ],
  "next_safe_actions": [
@@ -539,14 +551,14 @@
      "source_contract": "source_control_workflow_secret_name_inventory_v1",
      "allowed_processing": [
        "顯示 8 個 candidate repos 的 inventory lanes、4 個 repos 的 local evidence 與 7 個 repos 的 redacted export request",
-        "顯示 S4.12 owner response request packet、template statuses、templates、received_response_count=0 與 rejection rules",
+        "顯示 S4.12 owner response request packet、template statuses、audit event templates、templates、received_response_count=0 與 rejection rules",
        "要求 repo owner 補 redacted workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 snapshot",
        "顯示 GitHub hosted runner 額度風險與 self-hosted runner owner review lane",
        "response 通過後只更新 read-only inventory、export request 與 readiness blocker wording",
        "只保存 secret name、owner 與 present/absent metadata，不保存 value"
      ],
      "blocked_processing": [
-        "把 S4.12 request packet、template status ledger 或 response packet 當成 workflow 修改、secret 建立、runner 啟用或 primary approval",
+        "把 S4.12 request packet、template status ledger、audit event templates 或 response packet 當成 workflow 修改、secret 建立、runner 啟用或 primary approval",
        "收集或保存 secret value",
        "修改 workflow 或 webhook",
        "啟用 GitHub hosted runner 或消耗 GitHub Actions 額度",
@@ -590,7 +602,7 @@
    "S4.9 只新增 Gitea owner attestation response request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks 與 response 收件包；owner_response_request_packet_count=1、owner_response_template_status_count=5、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、owner_response_display_section_count=8、owner_response_collection_check_count=6、required_response_item_count=5、received_response_count=0、accepted_response_count=0、audit_events_emitted=0，不把 request packet、template status ledger、audit event templates、redaction examples、display sections、collection checks 或 response packet 當 inventory 執行、audit production ingestion 或 primary approval。",
    "S4.10 新增 GitHub target owner decision response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包；owner_response_request_packet_count=1、owner_response_template_status_count=7、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、owner_response_collection_check_count=6、intake_preflight_check_count=6、response_template_count=7、received_response_count=0、accepted_response_count=0，不把 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當 repo creation、visibility change、refs sync 或 GitHub primary approval。",
    "S4.11 已新增 refs truth owner response request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 與收件包；owner_response_request_packet_count=1、owner_response_template_status_count=5、owner_response_audit_event_template_count=3、owner_response_redaction_example_count=5、owner_response_collection_check_count=6、intake_preflight_check_count=6、response_template_count=5、received_response_count=0、accepted_response_count=0、audit_events_emitted=0，不把 request packet、template status ledger、audit event templates、redaction examples、collection checks、intake preflight checks 或 response packet 當 refs sync、delete、force push 或 GitHub primary approval。",
-    "S4.12 只新增 workflow / secret 名稱 owner response request packet、template status ledger 與收件包；response_template_count=5、received_response_count=0、accepted_response_count=0，不把 request packet、template status ledger 或 response packet 當 secret value collection、workflow modification、GitHub hosted runner enablement 或 GitHub primary approval。",
+    "S4.12 只新增 workflow / secret 名稱 owner response request packet、template status ledger、audit event templates 與收件包；owner_response_audit_event_template_count=3、audit_events_emitted=0、response_template_count=5、received_response_count=0、accepted_response_count=0，不把 request packet、template status ledger、audit event templates 或 response packet 當 secret value collection、workflow modification、GitHub hosted runner enablement 或 GitHub primary approval。",
    "S4.13 只新增 owner response validation rollup；response_packet_count=4、template_count=22、received_response_count=0、accepted_response_count=0、cross_packet_check_count=10、next_collection_candidate=S4.9，不把 rollup 當 approval、runtime gate 或 execution authorization。"
  ],
  "forbidden_actions": [
--- a/docs/security/security-supply-chain-contract-manifest.snapshot.json
+++ b/docs/security/security-supply-chain-contract-manifest.snapshot.json
@@ -637,7 +637,7 @@
        "sync_refs",
        "switch_github_primary"
      ],
-      "notes": "定義 S4.1 workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 契約；S4.2 已補 local evidence：4 repos、31 workflow files、43 個 referenced secret names；S4.3 已補 7 repos / 5 lanes 的 redacted export request；S4.12 已補 1 個 owner response request packet、5 個 template statuses 與 5 個 owner response templates，received_response_count=0；仍不保存 secret value。"
+      "notes": "定義 S4.1 workflow / webhook / runner / deploy key / branch protection / CODEOWNERS / secret 名稱 inventory 契約；S4.2 已補 local evidence：4 repos、31 workflow files、43 個 referenced secret names；S4.3 已補 7 repos / 5 lanes 的 redacted export request；S4.12 已補 1 個 owner response request packet、5 個 template statuses、3 個 audit event templates 與 5 個 owner response templates，received_response_count=0、audit_events_emitted=0；仍不保存 secret value。"
    },
    {
      "contract": "local_repo_canonical_probe_v1",
--- a/docs/security/source-control-owner-response-validation-rollup.snapshot.json
+++ b/docs/security/source-control-owner-response-validation-rollup.snapshot.json
@@ -139,7 +139,7 @@
      "source_contract": "source_control_workflow_secret_name_owner_response_v1",
      "response_packet": "docs/security/source-control-workflow-secret-name-owner-response.snapshot.json",
      "human_doc": "docs/security/SOURCE-CONTROL-WORKFLOW-SECRET-NAME-OWNER-RESPONSE.md",
-  "scope_summary": "webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted owner response request / response。",
+      "scope_summary": "webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的 redacted owner response request / template status ledger / audit event templates / response。",
      "response_template_count": 5,
      "received_response_count": 0,
      "accepted_response_count": 0,
@@ -147,9 +147,10 @@
      "required_before_ready": [
        "每個 lane 只能保存允許欄位與脫敏 metadata",
        "GitHub hosted runner 只能進 risk review，不得啟用或消耗 hosted minutes",
-    "secret name parity 只保存名稱、scope、owner 與 present/absent，不保存 value/hash/partial token",
-    "request packet 只提示 owner 要回覆什麼，不代表 request sent、response received、secret value collection、workflow modification 或 runner enablement",
-    "template status ledger 只逐項顯示 waiting_owner_response，不代表 request sent、response received 或 accepted"
+        "secret name parity 只保存名稱、scope、owner 與 present/absent，不保存 value/hash/partial token",
+        "request packet 只提示 owner 要回覆什麼，不代表 request sent、response received、secret value collection、workflow modification 或 runner enablement",
+        "template status ledger 只逐項顯示 waiting_owner_response，不代表 request sent、response received 或 accepted",
+        "audit event templates 只定義 0 emitted 的脫敏 metadata，不代表 production ingestion 或 runtime authorization"
      ],
      "allowed_outputs": [
        "更新 read-only workflow / secret name inventory wording",
@@ -292,7 +293,7 @@
    },
    {
      "effect_id": "workflow_secret_owner_response_accepted",
-      "when_all_checks_pass": "S4.12 request packet 與 template status ledger 只作顯示，5 個 workflow / secret lanes 全部接受，且所有 evidence 已脫敏。",
+      "when_all_checks_pass": "S4.12 request packet、template status ledger 與 audit event templates 只作顯示，5 個 workflow / secret lanes 全部接受，且所有 evidence 已脫敏。",
      "allowed_update": "只更新 workflow / secret name inventory、redacted export request 與 readiness wording。",
      "still_forbidden": [
        "store_secret_value",
@@ -368,7 +369,7 @@
      "received_response_count": 0,
      "accepted_response_count": 0,
      "current_status": "waiting_owner_response",
-      "next_owner_action": "Owner 需依 S4.12 request packet 回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的脫敏狀態；template status ledger 會維持 waiting，直到實際收到脫敏 response。",
+      "next_owner_action": "Owner 需依 S4.12 request packet、template status ledger 與 audit event templates 回覆 webhook、runner、deploy key、branch protection / CODEOWNERS、repository secret name parity 的脫敏狀態；template status ledger 會維持 waiting、audit event templates 維持 0 emitted，直到實際收到脫敏 response。",
      "awooop_display_mode": "observe_missing_response",
      "still_forbidden": [
        "store_secret_value",
--- a/docs/security/source-control-primary-readiness-gate.snapshot.json
+++ b/docs/security/source-control-primary-readiness-gate.snapshot.json
@@ -103,13 +103,13 @@
      ],
      "current_gap": [
        "S4.1 已定義 workflow / webhook / runner / secret 名稱 inventory 契約，但尚未收集實際 redacted snapshot",
-        "S4.12 已建立 workflow / secret 名稱 owner response 收件包，但目前 received_response_count=0、accepted_response_count=0",
+        "S4.12 已建立 workflow / secret 名稱 owner response request packet、template status ledger、audit event templates 與收件包，但目前 received_response_count=0、accepted_response_count=0、audit_events_emitted=0",
        "不得搬移或輸出 secret value",
        "不得因缺資料而假設 GitHub ready"
      ],
      "allowed_now": [
        "建立 read-only inventory plan",
-        "mirror S4.12 owner response templates、acceptance checks 與 rejection rules",
+        "mirror S4.12 owner response request packet、template status ledger、audit event templates、templates、acceptance checks 與 rejection rules",
        "列出需要 owner 補證的欄位",
        "維持 GitHub primary blocked"
      ],
--- a/docs/security/source-control-workflow-secret-name-inventory.snapshot.json
+++ b/docs/security/source-control-workflow-secret-name-inventory.snapshot.json
@@ -427,7 +427,7 @@
    "此 inventory 完成前，GitHub primary readiness gate 必須維持 blocked。",
    "S4.2 已補本機可見 workflow / CODEOWNERS / referenced secret name evidence，但 webhook、deploy key、branch protection 與 repository secret parity 仍未完成。",
    "S4.3 已補 redacted export request package，將 webhook、runner、deploy key、branch protection/CODEOWNERS 與 repository secret name parity 的 owner / read-only export 欄位、拒收欄位與 acceptance gate 文件化；它仍不是 API 執行或 primary cutover 批准。",
-    "S4.12 已補 owner response request packet、template status ledger 與收件包，將 5 類 export lanes 的 request 欄位、等待狀態、response 欄位、驗收規則與拒收規則文件化；received_response_count=0，仍不得收集 secret value 或修改 workflow。",
+    "S4.12 已補 owner response request packet、template status ledger、audit event templates 與收件包，將 5 類 export lanes 的 request 欄位、等待狀態、0 emitted 脫敏 audit metadata 模板、response 欄位、驗收規則與拒收規則文件化；received_response_count=0、audit_events_emitted=0，仍不得收集 secret value 或修改 workflow。",
    "inventory snapshot 只能 mirror 成 Operator Console / Audit evidence，不得新增 execution action。"
  ],
  "forbidden_actions": [
--- a/docs/security/source-control-workflow-secret-name-owner-response.snapshot.json
+++ b/docs/security/source-control-workflow-secret-name-owner-response.snapshot.json
@@ -28,6 +28,7 @@
    "local_referenced_secret_name_count": 43,
    "owner_response_request_packet_count": 1,
    "owner_response_template_status_count": 5,
+    "owner_response_audit_event_template_count": 3,
    "response_template_count": 5,
    "received_response_count": 0,
    "accepted_response_count": 0,
@@ -258,6 +259,184 @@
      ]
    }
  ],
+  "owner_response_audit_event_templates": [
+    {
+      "event_template_id": "audit-workflow-secret-response-request-shown",
+      "display_order": 1,
+      "event_status": "template_only_not_emitted",
+      "trigger": "AwoooP 顯示 S4.12 workflow / secret name owner response request packet 時。",
+      "purpose": "只記錄 request packet 顯示 metadata；不代表 request 已送出、owner response 已收到、secret value collection、workflow / webhook / runner / deploy key / branch protection / repository secret 修改或 GitHub primary 授權。",
+      "allowed_metadata_fields": [
+        "event_id",
+        "event_time_taipei",
+        "event_template_id",
+        "source_contract",
+        "target_contract",
+        "request_id",
+        "requested_template_ids",
+        "displayed_by_role",
+        "displayed_to_owner_role_or_team",
+        "repo_count",
+        "lane_count",
+        "source_document_ref",
+        "redaction_status"
+      ],
+      "forbidden_payloads": [
+        "secret_value",
+        "token_value",
+        "private_key",
+        "deploy_key_value",
+        "runner_registration_token",
+        "runner_admin_token",
+        "webhook_secret",
+        "cookie_or_session",
+        "authorization_header",
+        "complete_webhook_payload_url",
+        "query_token",
+        "request_body",
+        "response_body",
+        "secret_hash",
+        "masked_token",
+        "partial_credential",
+        "workflow_modification_request",
+        "webhook_modification_request",
+        "runner_enablement_request",
+        "deploy_key_rotation_request",
+        "branch_protection_change_request",
+        "repository_secret_change_request",
+        "github_hosted_runner_enable_request",
+        "refs_sync_request",
+        "github_primary_switch_request",
+        "execution_request_payload",
+        "unredacted_screenshot"
+      ],
+      "emitted_event_count": 0,
+      "stored_raw_payload_allowed": false,
+      "awooop_display_mode": "display_audit_template_only",
+      "execution_authorized": false,
+      "not_approval": true
+    },
+    {
+      "event_template_id": "audit-workflow-secret-response-received-metadata",
+      "display_order": 2,
+      "event_status": "template_only_not_emitted",
+      "trigger": "Owner 提供 S4.12 workflow / secret name response metadata pointer 時。",
+      "purpose": "只記錄已收到脫敏 metadata pointer；不得保存 owner response raw body、secret value、token、runner token、webhook secret、private key、deploy key value、完整 URL credential、request body、response body 或未脫敏截圖。",
+      "allowed_metadata_fields": [
+        "event_id",
+        "event_time_taipei",
+        "event_template_id",
+        "source_contract",
+        "request_id",
+        "template_id",
+        "lane",
+        "repo",
+        "provider",
+        "owner_role_or_team",
+        "decision",
+        "decision_reason_summary",
+        "evidence_refs",
+        "redaction_status",
+        "quarantine_lane",
+        "next_owner_action"
+      ],
+      "forbidden_payloads": [
+        "secret_value",
+        "token_value",
+        "private_key",
+        "deploy_key_value",
+        "runner_registration_token",
+        "runner_admin_token",
+        "webhook_secret",
+        "cookie_or_session",
+        "authorization_header",
+        "complete_webhook_payload_url",
+        "query_token",
+        "request_body",
+        "response_body",
+        "secret_hash",
+        "masked_token",
+        "partial_credential",
+        "workflow_modification_request",
+        "webhook_modification_request",
+        "runner_enablement_request",
+        "deploy_key_rotation_request",
+        "branch_protection_change_request",
+        "repository_secret_change_request",
+        "github_hosted_runner_enable_request",
+        "refs_sync_request",
+        "github_primary_switch_request",
+        "execution_request_payload",
+        "unredacted_screenshot"
+      ],
+      "emitted_event_count": 0,
+      "stored_raw_payload_allowed": false,
+      "awooop_display_mode": "display_audit_template_only",
+      "execution_authorized": false,
+      "not_approval": true
+    },
+    {
+      "event_template_id": "audit-workflow-secret-response-outcome-classified",
+      "display_order": 3,
+      "event_status": "template_only_not_emitted",
+      "trigger": "AwoooP 依 S4.12 acceptance checks 與 rejection rules 分類 workflow / secret name owner response 時。",
+      "purpose": "只記錄分類結果、reviewer role 與下一步 owner action；不得把 outcome、owner wording 或單項 response 當成 secret value collection、workflow 修改、webhook 修改、runner 啟用、deploy key rotation、branch protection change、repository secret change、refs sync 或 GitHub primary 授權。",
+      "allowed_metadata_fields": [
+        "event_id",
+        "event_time_taipei",
+        "event_template_id",
+        "source_contract",
+        "request_id",
+        "template_id",
+        "lane",
+        "repo",
+        "provider",
+        "owner_role_or_team",
+        "decision",
+        "decision_reason_summary",
+        "latest_outcome_lane",
+        "evidence_refs",
+        "redaction_status",
+        "quarantine_lane",
+        "next_owner_action",
+        "reviewer_role"
+      ],
+      "forbidden_payloads": [
+        "secret_value",
+        "token_value",
+        "private_key",
+        "deploy_key_value",
+        "runner_registration_token",
+        "runner_admin_token",
+        "webhook_secret",
+        "cookie_or_session",
+        "authorization_header",
+        "complete_webhook_payload_url",
+        "query_token",
+        "request_body",
+        "response_body",
+        "secret_hash",
+        "masked_token",
+        "partial_credential",
+        "workflow_modification_request",
+        "webhook_modification_request",
+        "runner_enablement_request",
+        "deploy_key_rotation_request",
+        "branch_protection_change_request",
+        "repository_secret_change_request",
+        "github_hosted_runner_enable_request",
+        "refs_sync_request",
+        "github_primary_switch_request",
+        "execution_request_payload",
+        "unredacted_screenshot"
+      ],
+      "emitted_event_count": 0,
+      "stored_raw_payload_allowed": false,
+      "awooop_display_mode": "display_audit_template_only",
+      "execution_authorized": false,
+      "not_approval": true
+    }
+  ],
  "response_templates": [
    {
      "template_id": "response-webhook-redacted-export",