feat(web): show GitHub readiness in AwoooP tenants
This commit is contained in:
@@ -49,6 +49,7 @@
|
||||
| AwoooP contracts GitHub primary readiness candidate | S2.65 已在 `/awooop/contracts` 顯示 GitHub Primary Readiness 合約只讀候選;candidate repos=8、in-scope=7、primary_ready_count=0、owner response 0/22、workflow inventory complete=0/7;仍不建立 repo、不改 visibility、不改 refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| AwoooP approvals GitHub primary readiness boundary | S2.66 已在 `/awooop/approvals` 顯示 GitHub Primary Readiness 審批邊界;S4.9=0/5、S4.10=0/7、S4.11=0/5、S4.12=0/5、primary_ready_count=0;仍不建立 approval record、不建立 repo、不改 visibility、不改 refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| AwoooP home GitHub primary readiness summary | S2.67 已在 `/awooop` 顯示 GitHub Primary Readiness 只讀摘要;candidate repos=8、in-scope=7、primary_ready_count=0、owner response 0/22、workflow inventory complete=0/7;仍不建立 repo、不改 visibility、不改 refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| AwoooP tenants GitHub primary readiness scope | S2.68 已在 `/awooop/tenants` 顯示 GitHub Primary Readiness 租戶範圍;candidate repos=8、in-scope=7、owner response 0/22、tenant scope changes=0;仍不改 migration mode、不改 tenant policy、不建立 repo、不改 visibility、不改 refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| 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` |
|
||||
| Payload ingestion | `false` |
|
||||
@@ -164,6 +165,7 @@
|
||||
| S2.65 AwoooP contracts GitHub primary readiness candidate | framework detail | 0 | 只在 `/awooop/contracts` 顯示 GitHub Primary Readiness 合約只讀候選,連回 `/iwooos` 並呈現 candidate repos=8、in-scope=7、primary_ready_count=0、owner response 0/22、workflow inventory complete=0/7;runtime_execution_authorized=false、active_runtime_gate_count=0、action_buttons_allowed=false、not_authorization=true,不建立 GitHub repo、不改 visibility、不 sync / delete / force push refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| S2.66 AwoooP approvals GitHub primary readiness boundary | framework detail | 0 | 只在 `/awooop/approvals` 顯示 GitHub Primary Readiness 審批邊界,連回 `/iwooos` 並呈現 S4.9=0/5、S4.10=0/7、S4.11=0/5、S4.12=0/5、primary_ready_count=0;approval_record_created=false、runtime_execution_authorized=false、active_runtime_gate_count=0、action_buttons_allowed=false、not_authorization=true,不建立 approval record、不建立 GitHub repo、不改 visibility、不 sync / delete / force push refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| S2.67 AwoooP home GitHub primary readiness summary | framework detail | 0 | 只在 `/awooop` 顯示 GitHub Primary Readiness 只讀摘要,連回 `/iwooos` 並呈現 candidate repos=8、in-scope=7、primary_ready_count=0、owner response 0/22、workflow inventory complete=0/7;repo_creation_authorized=false、refs_mutation_authorized=false、secret_value_collection_allowed=false、github_primary_switch_authorized=false、gitea_disablement_authorized=false、runtime_execution_authorized=false、active_runtime_gate_count=0、action_buttons_allowed=false、not_authorization=true,不建立 GitHub repo、不改 visibility、不 sync / delete / force push refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
| S2.68 AwoooP tenants GitHub primary readiness scope | framework detail | 0 | 只在 `/awooop/tenants` 顯示 GitHub Primary Readiness 租戶範圍,連回 `/iwooos` 並呈現 AWOOOI first tenant source-control scope、S4.9、S4.10、S4.12 owner scope refs、candidate repos=8、in-scope=7、owner response 0/22、tenant scope changes=0;tenant_source_control_scope_accepted=false、repo_owner_response_accepted=false、repo_creation_authorized=false、refs_mutation_authorized=false、github_primary_switch_authorized=false、gitea_disablement_authorized=false、tenant_policy_mutation_authorized=false、runtime_execution_authorized=false、active_runtime_gate_count=0、action_buttons_allowed=false、not_authorization=true,不改 migration mode、不改 tenant policy、不建立 GitHub repo、不改 visibility、不 sync / delete / force push refs、不收 secret value、不切 primary、不停用 Gitea |
|
||||
|
||||
headline 進度要再往上,至少需要下列任一高層 gate 有實質 evidence:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user