docs(security): 補 S4.9 owner response intake form [skip ci]

This commit is contained in:
Your Name
2026-06-05 10:59:30 +08:00
parent 37c0e1718b
commit a516d3f81f
3 changed files with 209 additions and 2 deletions

View File

@@ -9,7 +9,7 @@
| 工作視窗 | IwoooS / AWOOOI 資安治理 P0 |
| 本次乾淨 worktree | `/private/tmp/awoooi-p1-106-offsite-escrow-readiness-20260605` |
| 本次分支 | `codex/p1-305-velero-minio-freshness` |
| 最新觀察到的 `gitea/main` | `b615bde5 docs(security): 補 S4.9 owner response 缺口稽核 [skip ci]` |
| 最新觀察到的 `gitea/main` | `37c0e171 docs(governance): 對齊 P1-001 最新正式 deploy marker [skip ci]` |
| 最新 P2-D0 繁中文案基準 | code `cd2275a2`、deploy marker `1920bd08`、code-review `2565`、CD `2564` |
| 最新 P2-D1 本地掃描基準 | `VISIBLE_LITERAL_TARGET_SCAN_OK files=221`;全站 TS / TSX 中文 literal 盤點 `35` 檔 / `752` 行;註解語氣 backlog `32` 筆 |
| 最新 P2-D1 正式部署基準 | code `f9bf8a28`、deploy marker `879b0a36`、CD `2578`、code-review `2579` |
@@ -18,8 +18,10 @@
| 最新 P2-D2 Code Review 候選分類基準 | code `292cfec9`、deploy marker `4cfe5ff7`、CD `2586`、code-review `2587`Code Review route 可見文案已搬到 `codeReview` i18n namespace四類候選分類與人工批准流程已正式驗證 |
| 最新 P2-D2 AwoooP Runs fallback 文案基準 | code `7f6028c3`、deploy marker `bf016e91`、CD `2590`、code-review `2591`Runs / Callback / Source Flow fallback 文案已正式驗證 |
| 最新 AI Agent automation P1-305 / P1-306 基準 | code `4f0787f8`、deploy marker `af3a9d48`、CD `2592`、code-review `2593`任務批准邊界與進度彙總已正式驗證backlog `70%`、done `16/23`、下一步 `P1-001` |
| 最新 AI Agent automation P1-001 基準 | code `de3007b7`、stability fix `fd33591c`、deploy marker `8caba233`、LOGBOOK / marker 對齊 `37c0e171`runtime surface `22`、Secret surface `4`、live gaps `6`、backlog `74%`、done `17/23`、下一步 `P1-002` |
| 最新 S4.9 canonical owner response envelope 基準 | `docs/security/S4-9-CANONICAL-OWNER-RESPONSE-ENVELOPE.md`;六欄信封、欄位 alias、五題投影、quarantine-first 與 reviewer checklist 已固定owner response gate 仍 `0%` |
| 目前平行 Session | AwoooP thread `019e9154-7d5e-7b72-85be-c9d97e43ecc9` 正在推 `P1-001 runtime surface inventory`;本視窗避免修改同一批 runtime surface schema / API / UI 檔 |
| 最新 S4.9 owner response intake form 基準 | `docs/security/S4-9-OWNER-RESPONSE-INTAKE-FORM.md`五題可填表、六欄填寫規則、reviewer 收件欄與 outcome lanes 已固定owner response gate 仍 `0%` |
| 目前平行 Session | AwoooP thread `019e9154-7d5e-7b72-85be-c9d97e43ecc9` 正在推 `P1-002 Gitea 工作流程與 runner 健康合約盤點`;本視窗避免修改同一批 workflow / runner snapshot / API / UI 檔 |
| 前一個正式 IwoooS 候選基準 | code `7b8fc093`、deploy marker `45c63488`、LOGBOOK `02cadee6` |
| 最新導航 IA 基準 | code `973fc7a4`、LOGBOOK `2555c811`、deploy marker `0260ec89` |
| 禁止事項 | 不 force push、不 destructive git、不 SSH 修改主機、不 active scan、不收 secrets 明文、不把 AwoooP approval 當資安批准、不把 UI 可見當 runtime 授權 |
@@ -52,6 +54,7 @@
| P0-2b | S4.9 request dispatch preflight 交接包 | 100% | 送件前檢查、交接封套欄位與送後不變條件已固定dispatch authorized 仍 false | JSON parse、owner response guard、progress guard |
| P0-2c | S4.9 current gap audit | 100% | 已新增 `S4-9-OWNER-RESPONSE-GATE-CURRENT-GAP-AUDIT.md`,列出已符合、仍不符合、需新增、需調整、五題回覆與 0 / false 邊界owner response gate 仍 0% | owner response guard、progress guard、diff check |
| P0-2d | S4.9 canonical owner response envelope | 100% | 已新增 `S4-9-CANONICAL-OWNER-RESPONSE-ENVELOPE.md`固定六欄信封、source template alias mapping、五題投影、quarantine-first 與 reviewer checklistowner response gate 仍 0% | owner response guard、progress guard、diff check |
| P0-2e | S4.9 owner response intake form | 100% | 已新增 `S4-9-OWNER-RESPONSE-INTAKE-FORM.md`固定五題可填表、六欄填寫規則、reviewer 收件欄與 outcome lanesowner response gate 仍 0% | owner response guard、progress guard、diff check |
| P0-3 | AwoooP 同步封包 | 100% | 已送至 AwoooP 平行工作 thread `019e9154-7d5e-7b72-85be-c9d97e43ecc9`;後續仍需每次推版前重新 fetch / fast-forward | 本文件、thread send readback、mirror checklist readback |
| P0-4 | production live sanity 節點 | 100% | desktop / mobile / 展開區塊 / overflow / action href 檢查已完成 | Playwright production sanity 通過 |
| P0-5 | LOGBOOK 與完成度更新 | 100% | D2 comments-only、D2 AIOps sample、D2 Code Review 候選分類與 D2 AwoooP Runs fallback 皆已回填;可見 / bundle 變更皆已補 local / production desktop + mobile smoke | `docs/LOGBOOK.md` readback |
@@ -117,6 +120,17 @@ S4.9 是目前 IwoooS 64% 能往前的第一優先 gate。驗收前所有 count
| Quarantine-first | 100% | secret、token、private key、cookie、session、authorization header、未脫敏截圖與執行要求先隔離或拒收 | 不得渲染 raw payload不得寫入 LOGBOOK |
| Reviewer checklist | 100% | 六欄、五題、alias mapping、敏感 payload、執行要求、跨包一致性、count transition、gate boundary 已列入驗收前檢查 | 不得把 AwoooP approval 或 UI 可見當資安批准 |
### 3.6 2026-06-05 Owner Response Intake Form
本輪把 S4.9 從「canonical envelope 已固定」再推到「owner 可直接照表填五題」。這是表單準備度,不是 request sent、不代表 owner response received也不代表 accepted`request_sent=false``request_sent_count=0`、received / accepted / rejected 全部仍為 `0`
| 項目 | 完成度 | 目前狀態 | 不可誤讀 |
|------|--------|----------|----------|
| 五題可填表 | 100% | `response-public-only-vs-local-gitea-gap``response-org-user-endpoint-identity``response-internal-110-adjacent-scope``response-repo-owner-canonical-scope``response-legacy-or-inaccessible-disposition` 已各有六欄填寫表 | 不代表五題已送出或已回覆 |
| 六欄填寫規則 | 100% | owner role / team、decision、decision reason、affected scope、redacted evidence refs、followup owner 已逐欄說明 | 不代表收件完成 |
| Reviewer 收件欄 | 100% | 五題完整性、decision、scope、redacted refs、sensitive payload、執行要求、補證與 reviewer validation 已列檢查欄 | 不代表 accepted |
| Outcome lanes | 100% | waiting、request_more_evidence、quarantine、reject_execution_request、ready_for_reviewer_validation 已固定 | 不得開 action button 或 runtime gate |
## 4. 驗證節點規則
| 階段類型 | 必跑驗證 | 是否需要實際開頁 |
@@ -203,6 +217,7 @@ P1 只讀重盤階段整體完成度:`70%`。它代表 freshness / inventory /
| 需要調整規範 | Rollback ADR owner readiness | 舊 ADR 有 fallback / trigger / window 摘要,但缺可交接的 owner response 封套與逐 repo template | 已補 P1-5 handoff packagereceived / accepted / approved 仍全部 0 |
| 需要調整規範 | AwoooP 同步封包 | P1 要同步 refreshed counts、blocked gates、no-run 狀態,避免另一 Session 以舊 `117` heads / `141` items 繼續推進 | 本總帳與 LOGBOOK 會作為同步封包來源 |
| 需要調整規範 | S4.9 欄位同義詞混用 | `affected_repos``affected_sources``canonical_namespace``evidence_refs``review_owner` 等欄位容易和使用者要求的六欄封套混用 | 已新增 canonical owner response envelope 規範source template 可保留細分欄位,但收件 / 顯示 / LOGBOOK 必須映射回六欄 |
| 需要新增規範 | S4.9 owner 可填表單 | 既有 request draft 與 response package 有欄位與規則,但缺一份 owner 可直接逐題填寫、reviewer 可直接分類的六欄 intake form | 已新增 `S4-9-OWNER-RESPONSE-INTAKE-FORM.md`;表單可用但 request sent / received / accepted 仍全部 0 |
| 需要新增規範 | 111 / 168 開發主機 scope handoff | 原本只有 observe-only mapping缺 owner 可審的 scope boundary、credential refusal、rollback owner、validation metrics 與維護窗口欄位 | 已新增 P1-8 handoff、snapshot 與 schemahost execution 仍 `0%` |
| 需要調整規範 | 111 Ollama fallback wording | 111 是 ADR-110 local fallback evidence 範圍,不可被誤讀成可直接改 route、重啟 Ollama 或停止模型 | 已在 P1-8 固定 `fallback_route_change_authorized=false` 與 route truth observe-only |
| 需要調整規範 | 168 dev origin / repo hygiene wording | repo hygiene 與 local service exposure 容易被誤讀成可掃個人資料、讀未授權目錄或改 CORS / firewall | 已在 P1-8 固定未授權目錄、個人資料、secret derivative、CORS / firewall / service change 全部拒收 / 禁止 |
@@ -302,6 +317,7 @@ P1 只讀重盤階段整體完成度:`70%`。它代表 freshness / inventory /
| P2-D2 Code Review 候選分類 | code `292cfec9`、deploy marker `4cfe5ff7``/zh-TW/code-review` 可見文案搬進 `codeReview` namespacei18n mirror `9004` leavesTSX 中文 literal 命中 `0`;四類候選分類、人工批准流程、禁止 runtime 轉派與 `action_buttons_allowed=false` 可見typecheck、build、owner response guard、security mirror progress guard、diff check 通過Gitea code-review `2587` 成功、CD `2586` tests / build-and-deploy / post-deploy-checks 全部成功local / production desktop + mobile 均 `horizontalOverflow=0` |
| P2-D2 AwoooP Runs fallback 文案 | code `7f6028c3`、deploy marker `bf016e91``/zh-TW/awooop/runs`、Callback Evidence、Source Flow 與 status-chain fallback 可見文案已清理i18n mirror `9020` leaves目標殘留詞掃描命中 `0`typecheck、build、owner response guard、security mirror progress guard、diff check 通過Gitea code-review `2591` 成功、CD `2590` 成功local / production desktop + mobile 均 `horizontalOverflow=0`;截圖 `/tmp/awoooi-runs-callback-i18n-prod-desktop-bf016e91.png``/tmp/awoooi-runs-callback-i18n-prod-mobile-bf016e91.png` |
| S4.9 canonical owner response envelope | 新增 `docs/security/S4-9-CANONICAL-OWNER-RESPONSE-ENVELOPE.md`六欄信封、alias mapping、五題投影、quarantine-first、reviewer checklist 與驗收前 `0 / false` 邊界已固定;本段純文件,不改前端、不改 API、不新增 deployowner response gate 仍 `0%` |
| S4.9 owner response intake form | 新增 `docs/security/S4-9-OWNER-RESPONSE-INTAKE-FORM.md`五題可填表、六欄填寫規則、reviewer 收件欄、outcome lanes 與驗收前 `0 / false` 邊界已固定;本段純文件,不改前端、不改 API、不新增 deployowner response gate 仍 `0%` |
本輪驗證後仍維持: