@viccydev/pi-fpa 0.8.0 → 0.9.0

package/graphs/fpa-strategy-planning.json

@@ -0,0 +1,159 @@
+{
+  "schemaVersion": 1,
+  "name": "fpa-strategy-planning",
+  "version": "4.2.0",
+  "description": "FP&A 组合式策略规划：在一个 Graph 内完成目标规划、并行只读数据/驱动审计、并行只读场景分析、策略推荐与独立审核，最终形成 reviewed_strategy_handoff。必须提供字符串 context.scope_id、context.cycle_id、context.forecast_role；Graph 不审批、不预测、不发布仪表盘。",
+  "mutationPolicy": "mutating",
+  "start": "plan_cycle",
+  "maxSteps": 24,
+  "nodes": [
+    {
+      "id": "plan_cycle",
+      "type": "subagent",
+      "agentName": "plan_cycle",
+      "label": "目标与范围规划",
+      "outputKey": "plan_cycle",
+      "next": "parallel_analysis",
+      "systemPrompt": "你是 FP&A 目标规划 Agent。权威上下文为 scope_id={{context.scope_id}}、cycle_id={{context.cycle_id}}、forecast_role={{context.forecast_role}}。不得从目标文本猜测或替换这些标识。",
+      "prompt": "目标：{{goal}}\n\n按 fpa-plan-cycle 先调用 fpa_data_catalog 实测目标期和对比期字段可用性，再写 artifacts/planning_brief.md。明确目标、预算、周期、in_scope/out_of_scope 维度与指标、App 清单及增长/成熟/收缩角色。正式预测指标白名单仅为 spend、revenue、roas。不得生成策略、预测或调用任何 fpa_dashboard_* 工具。",
+      "skills": ["fpa-apply-core-rules", "fpa-plan-cycle"],
+      "tools": ["read", "write", "fpa_data_catalog"]
+    },
+    {
+      "id": "parallel_analysis",
+      "type": "parallel",
+      "label": "并行数据与经营审计",
+      "concurrency": 2,
+      "next": "synthesize_analysis",
+      "children": [
+        {
+          "id": "actuals_audit",
+          "type": "subagent",
+          "agentName": "actuals_audit",
+          "systemPrompt": "你是只读 FP&A 数据质量审计 Agent。不得写文件或发布仪表盘。",
+          "prompt": "目标：{{goal}}\n\n读取 artifacts/planning_brief.md，按 fpa-diagnose-actuals 检查数据窗口、字段覆盖、revenue 回刷成熟度、cohort 可用性、scope reduction 与 blocking issue。只输出结构化 JSON 证据给汇总节点，不写任何 artifact。",
+          "skills": ["fpa-apply-core-rules", "fpa-diagnose-actuals"],
+          "tools": ["read", "fpa_data_catalog", "fpa_query", "fpa_cohort"]
+        },
+        {
+          "id": "driver_audit",
+          "type": "subagent",
+          "agentName": "driver_audit",
+          "systemPrompt": "你是只读 FP&A 经营驱动审计 Agent。不得写文件或发布仪表盘。",
+          "prompt": "目标：{{goal}}\n\n读取 artifacts/planning_brief.md，按 in_scope_dimensions 独立查询 spend、revenue、roas、cpi、installs，分析组合、App、商店、渠道和平台驱动；明确每个 App/切片的增长、保持、削减或止损证据。只输出结构化 JSON，不写任何 artifact。",
+          "skills": ["fpa-apply-core-rules", "fpa-analyze-drivers"],
+          "tools": ["read", "fpa_query", "fpa_cohort", "fpa_compare", "fpa_calc"]
+        }
+      ]
+    },
+    {
+      "id": "synthesize_analysis",
+      "type": "subagent",
+      "agentName": "synthesize_analysis",
+      "label": "汇总上周期分析",
+      "outputKey": "driver_analysis",
+      "next": "parallel_scenarios",
+      "systemPrompt": "你是 FP&A 分析汇总 Agent。只整合并复核并行审计证据，不补造数据。",
+      "prompt": "目标：{{goal}}\n\n并行审计：{{data.parallel_analysis}}\n\n读取 planning_brief，交叉核对两个只读审计结果；冲突时重新用确定性工具复算。写 artifacts/actuals_snapshot.md、artifacts/data_issue_report.md、artifacts/driver_analysis.md 和机器可读 artifacts/driver_analysis.json。JSON 必须符合 driver_analysis contract，包含 artifact_type、status、headline_results、drivers、data_limits/limitations，并对每个 App 或 in-scope 切片给出增长/保持/削减/止损结论与证据。不得生成策略或发布仪表盘。",
+      "skills": ["fpa-apply-core-rules", "fpa-diagnose-actuals", "fpa-analyze-drivers"],
+      "tools": ["read", "write", "fpa_query", "fpa_compare", "fpa_calc"]
+    },
+    {
+      "id": "parallel_scenarios",
+      "type": "parallel",
+      "label": "并行策略场景分析",
+      "concurrency": 3,
+      "next": "synthesize_scenarios",
+      "children": [
+        {
+          "id": "efficiency_lane",
+          "type": "subagent",
+          "agentName": "efficiency_lane",
+          "systemPrompt": "你是只读 FP&A 稳健效率场景 Agent。不得写文件、批准策略或发布仪表盘。",
+          "prompt": "读取 planning_brief、actuals_snapshot 与 driver_analysis，构造维持硬 ROAS 下限的稳健/效率候选场景，逐 App/商店/渠道给出完整 allocation、downside/base/upside、假设和止损。只输出结构化 JSON 候选，不写 artifact。",
+          "skills": ["fpa-apply-core-rules", "fpa-simulate-strategies"],
+          "tools": ["read", "fpa_query", "fpa_calc"]
+        },
+        {
+          "id": "growth_lane",
+          "type": "subagent",
+          "agentName": "growth_lane",
+          "systemPrompt": "你是只读 FP&A 增长与探索场景 Agent。不得写文件、批准策略或发布仪表盘。",
+          "prompt": "读取 planning_brief、actuals_snapshot 与 driver_analysis，构造增长/探索候选场景；探索预算约 10%，逐 App/商店/渠道给出完整 allocation、downside/base/upside、假设和止损。只输出结构化 JSON 候选，不写 artifact。",
+          "skills": ["fpa-apply-core-rules", "fpa-simulate-strategies"],
+          "tools": ["read", "fpa_query", "fpa_calc"]
+        },
+        {
+          "id": "risk_lane",
+          "type": "subagent",
+          "agentName": "risk_lane",
+          "systemPrompt": "你是只读 FP&A 约束与风险挑战 Agent。不得写文件、批准策略或发布仪表盘。",
+          "prompt": "读取 planning_brief 与 driver_analysis，独立检查预算上下限、ROAS 硬下限、Revenue 次目标、ROAS<0.5 止损、集中度、外推和数据成熟度。输出每个候选策略必须满足的约束、压力测试区间与淘汰规则，只输出结构化 JSON。",
+          "skills": ["fpa-apply-core-rules", "fpa-simulate-strategies"],
+          "tools": ["read", "fpa_query", "fpa_calc"]
+        }
+      ]
+    },
+    {
+      "id": "synthesize_scenarios",
+      "type": "subagent",
+      "agentName": "synthesize_scenarios",
+      "label": "汇总候选策略",
+      "outputKey": "strategy_scenarios",
+      "next": "recommend_strategy",
+      "systemPrompt": "你是 FP&A 场景汇总 Agent。所有加总、ROAS 和约束判断必须确定性复算。",
+      "prompt": "目标：{{goal}}\n\n并行场景与风险审计：{{data.parallel_scenarios}}\n\n读取权威上游工件，合并、去重并复算候选场景，至少保留现状、稳健和增长场景。写 artifacts/strategy_scenarios.md 与符合 contract 的 artifacts/strategy_scenarios.json；逐切片完整覆盖，探索/利用分开，所有 ROAS<0.5 切片必须削减或清零。不得推荐、批准、预测或发布仪表盘。",
+      "skills": ["fpa-apply-core-rules", "fpa-simulate-strategies"],
+      "tools": ["read", "write", "fpa_calc"]
+    },
+    {
+      "id": "recommend_strategy",
+      "type": "subagent",
+      "agentName": "recommend_strategy",
+      "label": "形成执行策略",
+      "outputKey": "strategy_proposal",
+      "next": "review_strategy",
+      "systemPrompt": "你是 FP&A 策略推荐 Agent。不得自我批准、生成预测或发布仪表盘。",
+      "prompt": "目标：{{goal}}\n\n读取 planning_brief、driver_analysis 和 strategy_scenarios，按 fpa-recommend-strategy 选择推荐策略。写 artifacts/strategy_proposal.md 与符合 contract 的 artifacts/strategy_proposal.json。allocation 必须逐 App/商店/渠道包含显式 action（grow/hold/cut/stop）、spend 与 change_from_baseline，使 Dashboard 能明确展示增长、保持、削减和止损；保留完整 expected_outcomes、理由、风险、阈值和 required_human_decisions。",
+      "skills": ["fpa-apply-core-rules", "fpa-recommend-strategy"],
+      "tools": ["read", "write", "fpa_calc"]
+    },
+    {
+      "id": "review_strategy",
+      "type": "subagent",
+      "agentName": "review_strategy",
+      "label": "独立审核",
+      "outputKey": "strategy_review",
+      "parseJson": true,
+      "next": "route_review",
+      "systemPrompt": "你是未参与推荐生成的 FP&A 独立审核 Agent。不得批准策略、生成预测或发布仪表盘。",
+      "prompt": "读取 proposal 及全部上游机器工件，按 fpa-review-strategy 独立复算覆盖、加总、ROAS、止损、探索占比、外推与数据血缘。写 artifacts/strategy_review.md 和 artifacts/strategy_review.json。最终只输出路由 JSON：{\"status\":\"support|support_with_conditions|reject\",\"summary\":\"...\",\"conditions\":[]}。",
+      "skills": ["fpa-apply-core-rules", "fpa-review-strategy"],
+      "tools": ["read", "write", "fpa_query", "fpa_calc"]
+    },
+    {
+      "id": "route_review",
+      "type": "router",
+      "label": "审核结果路由",
+      "path": "data.strategy_review.status",
+      "cases": [
+        { "equals": "reject", "label": "审核拒绝，重新推荐", "to": "recommend_strategy" },
+        { "equals": "support", "label": "审核支持", "to": "prepare_strategy_handoff" },
+        { "equals": "support_with_conditions", "label": "有条件支持", "to": "prepare_strategy_handoff" }
+      ],
+      "default": { "label": "其他结果，重新推荐", "to": "recommend_strategy" }
+    },
+    {
+      "id": "prepare_strategy_handoff",
+      "type": "subagent",
+      "agentName": "prepare_strategy_handoff",
+      "label": "形成已审核策略交接",
+      "outputKey": "strategy_handoff",
+      "parseJson": true,
+      "systemPrompt": "你是 FP&A 策略交接 Agent。权威上下文为 scope_id={{context.scope_id}}、cycle_id={{context.cycle_id}}、forecast_role={{context.forecast_role}}。不批准、不预测、不发布仪表盘。",
+      "prompt": "读取 planning_brief、driver_analysis.json、strategy_scenarios.json、strategy_proposal.json 与 strategy_review.json，先调用 fpa_json_fingerprint 对 proposal/review 两个 JSON 生成确定性 SHA-256，再严格按 fpa-review-strategy 的 reviewed_strategy_handoff contract 核验并写 artifacts/reviewed_strategy_handoff.json。ready 文件必须包含 kind=fpa.reviewed-strategy-handoff、scope_id/cycle_id/forecast_role、相同的 strategy_version 与 reviewed_strategy_version、工具返回的 proposal/review fingerprint、独立审核身份、review_opinion、条件、剩余风险和 next_graph=fpa-forecast-freeze；失败时写 blocked 结果且不得覆盖已有 ready 文件。最终只输出 fpa.graph-handoff JSON。Graph 到此结束，由主 Agent 依次发布 period-review 与 next-strategy 模块并等待用户决策。",
+      "skills": ["fpa-apply-core-rules", "fpa-review-strategy"],
+      "tools": ["read", "write", "fpa_json_fingerprint"]
+    }
+  ]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viccydev/pi-fpa",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "type": "module",
   "description": "Full-cycle FP&A planning, strategy, forecast, and review prompts, skills, and data tools for Pi",
   "license": "UNLICENSED",
@@ -31,7 +31,7 @@
 		"fpa-dashboard-worker": "./bin/fpa-dashboard-worker.mjs"
 	},
   "scripts": {
-		"test": "node tests/package-structure.test.mjs && node tests/workflow-routing.test.mjs && node --test tests/workflow-routing-guard.test.mjs tests/graph-contract.test.mjs && node tests/extension-unit.test.mjs && node --test tests/catalog-timeout.test.mjs tests/artifact-store.test.mjs tests/artifact-ledger.test.mjs tests/artifact-handoff.test.mjs tests/forecast-compose.test.mjs tests/dashboard-actuals.test.mjs tests/dashboard-projector.test.mjs tests/dashboard-module-publisher.test.mjs tests/dashboard-stage-projector.test.mjs tests/strategy-decision.test.mjs tests/cycle-operating-projection.test.mjs tests/forward-outlook.test.mjs tests/forecast-accuracy.test.mjs tests/dashboard-publisher.test.mjs tests/dashboard-provenance.test.mjs tests/dashboard-coordinator.test.mjs && node tests/pi-loader-smoke.mjs && node tests/worker-loader-smoke.mjs && node tests/publish-workflow.test.mjs",
+		"test": "node tests/package-structure.test.mjs && node tests/workflow-routing.test.mjs && node --test tests/workflow-routing-guard.test.mjs tests/graph-contract.test.mjs tests/graph-installer.test.mjs && node tests/extension-unit.test.mjs && node --test tests/catalog-timeout.test.mjs tests/artifact-store.test.mjs tests/artifact-ledger.test.mjs tests/artifact-handoff.test.mjs tests/forecast-compose.test.mjs tests/dashboard-actuals.test.mjs tests/dashboard-projector.test.mjs tests/dashboard-module-publisher.test.mjs tests/dashboard-stage-projector.test.mjs tests/strategy-decision.test.mjs tests/cycle-operating-projection.test.mjs tests/forward-outlook.test.mjs tests/forecast-accuracy.test.mjs tests/dashboard-publisher.test.mjs tests/dashboard-provenance.test.mjs tests/dashboard-coordinator.test.mjs && node tests/pi-loader-smoke.mjs && node tests/worker-loader-smoke.mjs && node tests/publish-workflow.test.mjs",
     "test:structure": "node tests/package-structure.test.mjs",
 		"test:unit": "node tests/extension-unit.test.mjs && node --test tests/catalog-timeout.test.mjs tests/artifact-store.test.mjs tests/artifact-ledger.test.mjs tests/artifact-handoff.test.mjs tests/forecast-compose.test.mjs tests/dashboard-actuals.test.mjs tests/dashboard-projector.test.mjs tests/dashboard-module-publisher.test.mjs tests/dashboard-stage-projector.test.mjs tests/strategy-decision.test.mjs tests/cycle-operating-projection.test.mjs tests/forward-outlook.test.mjs tests/forecast-accuracy.test.mjs tests/dashboard-publisher.test.mjs tests/dashboard-provenance.test.mjs tests/dashboard-coordinator.test.mjs",
     "test:loader": "node tests/pi-loader-smoke.mjs && node tests/worker-loader-smoke.mjs",

package/prompts/fpa-plan-cycle.md

@@ -17,19 +17,19 @@ argument-hint: "<project-root> <cycle-id> [instructions]"
 ## 强制 Graph 路由
 
 先读取 `fpa-apply-core-rules`。如果当前 Agent 提供 `graph_list` 和
-`graph_run`，必须先调用 `graph_list`，确认 `fpa-period-analysis` 与
-`fpa-strategy-recommendation` 后按以下边界执行：
-
-1. 以完整用户目标、项目根、周期边界、业务范围和数据上下文运行
-   `fpa-period-analysis`。Graph 返回 `artifacts/driver_analysis.json` 后，父
-   Agent 调用 `fpa_dashboard_publish_review` 先 preview，再用精确
-   fingerprint/revision 发布 `period-review`。
-2. 再运行 `fpa-strategy-recommendation`。Graph 返回
-   `strategy_proposal.json` 与 `reviewed_strategy_handoff.json` 后，父 Agent
-   调用 `fpa_dashboard_publish_strategy` preview/publish，发布
+`graph_run`，必须先调用 `graph_list`，确认 `fpa-strategy-planning` 后按以下边界执行：
+
+1. 以完整用户目标运行一个组合式 `fpa-strategy-planning`。`graph_run.context`
+   的所有值必须是字符串，并明确提供 `scope_id`、`cycle_id`、
+   `forecast_role`；对象、数组、数字和其他结构化要求全部留在 `goal`。
+2. Graph 返回 `driver_analysis.json`、`strategy_proposal.json`、
+   `strategy_review.json` 与 `reviewed_strategy_handoff.json` 后，父 Agent 先调用
+   `fpa_dashboard_publish_review` preview/publish，取得最新 revision；再调用
+   `fpa_dashboard_publish_strategy`，传入 proposal/review/handoff 三个路径及精确
+   `scope_id`、`cycle_id`、`forecast_role` 做 preview/publish，发布
    `next-strategy` 并等待仪表盘决策。
 
-两个 Graph 都不得拥有或调用任何 `fpa_dashboard_*` 工具。发布是父 Agent
+Graph 不得拥有或调用任何 `fpa_dashboard_*` 工具。发布是父 Agent
 在 Graph 返回后的职责；父 Agent不得自行模拟 Graph 内的业务阶段。
 
 如果匹配 Graph 不在 catalog 中或无法加载，列出缺口并保持 `blocked`；不得把
@@ -39,7 +39,7 @@ Graph 返回业务阻塞同样不构成降级理由。所需上下文缺失时
 ## 不可跳过的停点
 
 - 策略推荐者不得批准或独立复核自己的提案。若宿主不能证明复核上下文与提案作者独立，复核阶段必须报告 `blocked`。
-- 独立复核完成后，`fpa-strategy-recommendation` 必须生成精确绑定提案与复核版本的 `reviewed_strategy_handoff`，然后停止。
+- 独立复核完成后，`fpa-strategy-planning` 必须生成精确绑定提案与复核版本的 `reviewed_strategy_handoff`，然后停止。
 - 聊天中的认可、模型自我确认或 Forecast 授权都不等于策略执行授权。
 - 仪表盘响应回到原主会话后，先由主 Agent 调用
   `fpa_strategy_decision_commit`。只有 `confirm` 成功才可在后续运行

package/skills/fpa-apply-core-rules/SKILL.md

@@ -20,18 +20,18 @@ writing artifacts. It applies only when the current agent exposes both
 
    | Eligible request and evidence | Required Graph |
    | --- | --- |
-   | New or changed objective requiring planning, Actuals diagnosis, and driver analysis | `fpa-period-analysis` |
-   | Completed `driver_analysis` requiring scenarios, recommendation, and independent review | `fpa-strategy-recommendation` |
+   | New or changed objective requiring planning, Actuals diagnosis, driver analysis, scenarios, recommendation, and independent review | `fpa-strategy-planning` |
    | Ready `reviewed_strategy_handoff` plus an exact confirmed `strategy_decision` and a request for an official forecast | `fpa-forecast-freeze` |
    | Exact committed approved Forecast ref plus an authorized execution request | `fpa-strategy-execution` |
    | Exact Forecast and Execution refs plus newly arrived comparable Actuals | `fpa-cycle-review` |
 
-3. Call `graph_run` with the user's complete goal and the exact immutable
-   context required by that Graph. The parent agent must not reproduce its
-   nodes or pre-run their `fpa_*` calls. After a successful Graph handoff, the
-   main Agent must publish only that stage's module with the matching
-   `fpa_dashboard_publish_*` tool. Graph nodes must never receive dashboard
-   publication tools.
+3. Call `graph_run` with the user's complete goal. Every `context` value must
+   be a string; provide exact `scope_id`, `cycle_id`, and `forecast_role`, and
+   keep structured planning details in `goal`. The parent agent must not
+   reproduce Graph nodes or pre-run their `fpa_*` calls. After the combined
+   planning Graph succeeds, the main Agent publishes `period-review` and then
+   `next-strategy` with their matching `fpa_dashboard_publish_*` tools. Graph
+   nodes must never receive dashboard publication tools.
 4. If required context is missing or ambiguous, return `blocked` and request
    the exact identity or ref. Do not fall back to direct phase execution.
 

package/skills/fpa-apply-core-rules/references/core-rules.md

@@ -2,20 +2,18 @@
 
 ## 1. Workflow and artifacts
 
-Period-analysis workflow (`fpa-period-analysis`):
+Combined strategy-planning workflow (`fpa-strategy-planning`):
 
-`planning_brief -> actuals_snapshot + data_issue_report -> driver_analysis`
+`planning_brief -> parallel(actuals audit, driver audit) -> driver_analysis -> parallel(efficiency, growth, risk) -> strategy_scenarios -> strategy_proposal -> strategy_review -> reviewed_strategy_handoff`
 
-The calling main Agent publishes `period-review`, then starts the separate
-strategy-recommendation workflow (`fpa-strategy-recommendation`):
-
-`driver_analysis -> strategy_scenarios -> strategy_proposal -> strategy_review -> reviewed_strategy_handoff`
-
-Each Graph stops at its named handoff. Neither Graph may publish dashboard
-content. The strategy Graph does not
+The Graph stops at the reviewed strategy handoff and may not publish dashboard
+content. Parallel children are independent and read-only; sequential reducer
+nodes alone write the canonical artifacts. The strategy Graph does not
 approve the strategy, create an official forecast, or execute the allocation.
 
-The calling main Agent publishes the exact ready handoff through
+The calling main Agent first publishes the exact `driver_analysis` through
+`fpa_dashboard_publish_review`, then publishes the exact proposal, independent
+review, ready handoff, and immutable scope/cycle/role through
 `fpa_dashboard_publish_strategy`, waits for the dashboard response in the
 originating main session, and commits it with `fpa_strategy_decision_commit`.
 Dashboard publishing and decision commit tools are forbidden from every Graph
@@ -27,9 +25,9 @@ ready handoff plus the exact confirmed strategy-decision fingerprint:
 `reviewed_strategy_handoff + strategy_decision -> forecast_plan -> approved_cycle_forecast`
 
 The main Agent owns approval recording; the forecast Graph owns deterministic
-composition and artifact freezing. A rejected approval returns to a new
-`fpa-strategy-planning` version rather than modifying the reviewed proposal in
-place.
+composition and artifact freezing. A rejected approval reruns
+`fpa-strategy-planning` with the exact feedback and produces a new version
+rather than modifying the reviewed proposal in place.
 
 Execution is a separate `fpa-strategy-execution` workflow:
 

package/skills/fpa-diagnose-actuals/references/artifact-contract.md

@@ -31,6 +31,8 @@ checks:
     affected_scope: []
     evidence: string
     remediation: string
+    owner_role: data_steward
+    disposition: excluded_from_calculation | warning_only | blocking
 blocking_issues: []
 non_blocking_limits: []
 ```

package/skills/fpa-forecast-approved-strategy/SKILL.md

@@ -84,11 +84,23 @@ tool. `complete_with_limits` remains publishable when its limitations are
 explicit, while `blocked` is not. Do not hide a real defect to get through the
 gate.
 
+Upstream identity or coverage defects are non-blocking data limits. Preserve
+the full approved allocation, leave affected revenue and ROAS values `NULL`,
+and let `fpa_forecast_compose` emit `data_quality`, a coverage-labelled partial
+`conclusion`, and actionable repair items. Never delete a bad slice, turn it
+into zero spend, or renormalize the remaining allocation. The affected slice
+remains ineligible for Actuals comparison and execution until its mapping is
+fixed. Approval mismatch, duplicate or negative allocation, budget mismatch,
+invalid period/currency/role, and unauthorized execution remain blocking
+governance failures.
+
 ## Boundaries
 
 - Do not optimize, revise, or substitute the approved strategy while forecasting.
 - A required change invalidates the current approval and routes back to recommendation and review.
 - Unsupported KPIs remain `NULL` with a reason.
+- A partial conclusion must say it covers only calculable slices and must show
+  `calculable_spend_pct`; it must never be labelled portfolio ROAS.
 - Do not execute the strategy and do not start continuous monitoring.
 
 ## Completion

package/skills/fpa-forecast-approved-strategy/references/artifact-contract.md

@@ -41,6 +41,28 @@ calibration_policy:
   policy_version: string
 unsupported_metrics: []
 reconciliation_checks: []
+data_quality:
+  status: complete | partial | unavailable
+  planned_spend: number
+  calculable_spend: number
+  calculable_spend_pct: number  # 0..1; never renormalized
+  excluded_spend: number
+  issue_count: number
+  issues:
+    - issue_id: string
+      code: slice_key_not_in_actuals
+      severity: warning
+      slice: {app_id: string, store: string, channel_group: string}
+      affected_metrics: [actuals_comparison, revenue, roas, execution]
+      disposition: excluded_from_calculation
+      evidence: []
+      remediation: string
+      owner_role: data_steward
+conclusion:
+  status: available | available_with_limits | unavailable
+  scope: portfolio | calculable_slices | none
+  metrics: {spend: scenario_metric, revenue: scenario_metric, roas: scenario_metric}
+  warning: string | null
 frozen_at: timestamp
 ```
 
@@ -97,7 +119,10 @@ Rules the plan has to respect, because compose enforces them:
 
 - **Spend is a decision, not a prediction.** It is identical in all three scenarios, so a slice carries one `approved_spend`. Only revenue moves, through `roas`.
 - **A stopped slice has no ROAS.** `approved_spend: 0` means revenue 0 and `roas` null in all three scenarios — the contract derives ROAS as revenue/spend and calls a zero denominator null.
-- **Slice keys must be values `ua_spend` actually uses.** A plan naming `google_play` where the mart says `android` is rejected with the valid values listed. The single-placeholder App axis for a scoped-out portfolio is the one permitted exception.
+- **Slice keys are checked as real triples.** `app_code`, `platform`, and `media_source` must occur together in `ua_spend`; validating three independent value lists is insufficient. A mismatch is isolated as a data-quality limit: approved spend remains in the allocation and consolidated spend, while affected revenue/ROAS are `NULL`. The single-placeholder App axis for a scoped-out portfolio remains permitted.
+- **Do not hide partiality.** Compose reports planned, calculable, and excluded spend. Its partial conclusion covers only calculable slices; remaining spend is never scaled to 100%, and partial ROAS is never labelled portfolio ROAS.
+- **Data quality does not weaken governance.** Missing/mismatched approval, duplicate or negative allocation, invalid period/currency/forecast role, and budget reconciliation failures still block.
+- **Describe other upstream limits actionably.** For non-identity defects, each `unsupported_metrics` item should name the affected metric/scope, evidence, remediation, and data owner. Dashboard publication keeps these items visible even when `data_quality.status` is otherwise complete.
 - **`status` and `unsupported_metrics` must agree.** `complete` requires an empty list; `complete_with_limits` requires a non-empty one. Scope excluded upstream is neither.
 - **Do not hand-compute anything derived.** A ROAS rounded to four decimals misses the commit tolerance and costs a re-draft.
 

package/skills/fpa-recommend-strategy/SKILL.md

@@ -12,7 +12,7 @@ Load `$fpa-apply-core-rules` first. Recommend one plan while keeping alternative
 1. Consume `planning_brief`, `driver_analysis`, and `strategy_scenarios`.
 2. Remove scenarios that breach hard constraints.
 3. Rank remaining scenarios using the objective priorities and declared trade-off rule.
-4. Select one recommendation and specify exact allocation, changes from baseline, expected ranges, assumptions, and risks.
+4. Select one recommendation and specify exact allocation, an explicit `grow | hold | cut | stop` action for every App/store/channel row, changes from baseline, expected ranges, assumptions, and risks.
 5. State why rejected alternatives were not chosen.
 6. Define next-cycle evaluation thresholds; do not create a real-time monitoring obligation.
 7. Write `strategy_proposal` using [artifact-contract.md](references/artifact-contract.md).

package/skills/fpa-recommend-strategy/references/artifact-contract.md

@@ -12,6 +12,7 @@ allocation:
   - app_id: string
     store: string
     channel_group: string
+    action: grow | hold | cut | stop
     spend: number
     change_from_baseline: number
 expected_outcomes:
@@ -27,4 +28,4 @@ next_cycle_evaluation_thresholds: []
 required_human_decisions: []
 ```
 
-The total allocation must reconcile to the proposed total budget, and every allocation row must map to a simulated scenario row.
+The total allocation must reconcile to the proposed total budget, and every allocation row must map to a simulated scenario row. `action` is explicit and mandatory: use `grow` for a budget increase, `hold` for an unchanged allocation, `cut` for a non-zero reduction, and `stop` when the slice is removed or held at zero under a stop-loss decision.

package/skills/fpa-refresh-dashboard/SKILL.md

@@ -22,10 +22,13 @@ preserve every other module revision.
 
 1. After the analysis Graph returns `driver_analysis`, preview then publish
    `period-review` with `fpa_dashboard_publish_review`.
-2. After the strategy Graph returns the exact `strategy_proposal` and
-   `reviewed_strategy_handoff`, preview then publish `next-strategy` with
-   `fpa_dashboard_publish_strategy`. Publication binds its decision action to
-   the current main session; never copy or expose a session id in dashboard data.
+2. After the strategy Graph returns the exact `strategy_proposal`, independent
+   `strategy_review`, and `reviewed_strategy_handoff`, preview then publish
+   `next-strategy` with `fpa_dashboard_publish_strategy`. Supply all three paths
+   and the exact `scope_id`, `cycle_id`, and `forecast_role`; the tool verifies
+   fingerprints, review independence, opinion, conditions, and next-stage
+   binding. Publication binds its decision action to the current main session;
+   never copy or expose a session id in dashboard data.
 3. Stop and wait for the dashboard action. The Web host sends a canonical
    decision message back to the bound original session. In that session call
    `fpa_strategy_decision_commit` with the exact `action_id`.

package/skills/fpa-review-strategy/references/artifact-contract.md

@@ -23,3 +23,25 @@ reviewed_at: timestamp
 ```
 
 Set `independence_confirmed: false` and `status: blocked` if the reviewer also authored the proposal. Any unresolved critical finding requires `reject`.
+
+# `reviewed_strategy_handoff` contract
+
+```yaml
+kind: fpa.reviewed-strategy-handoff
+status: ready | blocked
+scope_id: string
+cycle_id: string
+forecast_role: string
+strategy_version: string
+reviewed_strategy_version: string
+proposal_fingerprint: sha256
+review_fingerprint: sha256
+reviewer_identity: string
+independence_confirmed: true
+review_opinion: support | support_with_conditions
+review_conditions: []
+review_residual_risks: []
+next_graph: fpa-forecast-freeze
+```
+
+`strategy_version` and `reviewed_strategy_version` must be identical and must bind the exact proposal reviewed. A rejected or non-independent review cannot produce a ready handoff.

package/graphs/fpa-period-analysis.json

@@ -1,10 +0,0 @@
-{
-  "name": "fpa-period-analysis",
-  "version": "1.0.0",
-  "start": "plan_cycle",
-  "nodes": [
-    { "id": "plan_cycle", "type": "subagent", "agentName": "plan_cycle", "next": "diagnose_actuals", "skills": ["fpa-plan-cycle"], "tools": ["read", "write", "fpa_data_catalog"], "prompt": "规划精确周期、范围、指标与边界；不得推荐策略或调用仪表盘工具。" },
-    { "id": "diagnose_actuals", "type": "subagent", "agentName": "diagnose_actuals", "next": "analyze_drivers", "skills": ["fpa-diagnose-actuals"], "tools": ["read", "write", "fpa_data_catalog", "fpa_query"], "prompt": "诊断 Actuals 完整性并写入工件；不得调用仪表盘工具。" },
-    { "id": "analyze_drivers", "type": "subagent", "agentName": "analyze_drivers", "skills": ["fpa-analyze-drivers"], "tools": ["read", "write", "fpa_query", "fpa_calc"], "prompt": "分析上周期驱动因素并写 artifacts/driver_analysis.json；不得推荐策略或调用仪表盘工具。" }
-  ]
-}

package/graphs/fpa-strategy-recommendation.json

@@ -1,11 +0,0 @@
-{
-  "name": "fpa-strategy-recommendation",
-  "version": "1.0.0",
-  "start": "simulate_strategies",
-  "nodes": [
-    { "id": "simulate_strategies", "type": "subagent", "agentName": "simulate_strategies", "next": "recommend_strategy", "skills": ["fpa-simulate-strategies"], "tools": ["read", "write", "fpa_query", "fpa_calc"], "prompt": "根据分析工件试算候选策略；不得批准、预测或发布仪表盘。" },
-    { "id": "recommend_strategy", "type": "subagent", "agentName": "recommend_strategy", "next": "review_strategy", "skills": ["fpa-recommend-strategy"], "tools": ["read", "write"], "prompt": "形成完整策略提案；不得自我批准或发布仪表盘。" },
-    { "id": "review_strategy", "type": "subagent", "agentName": "review_strategy", "next": "prepare_handoff", "skills": ["fpa-review-strategy"], "tools": ["read", "write", "fpa_calc"], "prompt": "独立复核策略并写审核工件；不得批准或发布仪表盘。" },
-    { "id": "prepare_handoff", "type": "subagent", "agentName": "prepare_handoff", "tools": ["read", "write"], "prompt": "仅在审核通过时形成 reviewed_strategy_handoff；停止，不批准、不预测、不发布仪表盘。" }
-  ]
-}