提交 graphify 知识图谱，方便按图查询架构而不用重扫文档。

Co-authored-by: Cursor <cursoragent@cursor.com>

graphify-out/memory/query_20260815_093803_why_does_reportcreatepage_connect_harmonyos_app_sh.md

@@ -0,0 +1,28 @@
+---
+type: "query"
+date: "2026-08-15T09:38:03.115977+00:00"
+question: "Why does ReportCreatePage connect HarmonyOS App Shell to Report Pipeline Stages?"
+contributor: "graphify"
+outcome: "useful"
+source_nodes: ["ReportCreatePage", "ReportResultPage", "HomePage", "ReportService", "Report Pipeline Skeleton", "Stage Protocol", "Report Task Polling"]
+---
+
+# Q: Why does ReportCreatePage connect HarmonyOS App Shell to Report Pipeline Stages?
+
+## Answer
+
+Expanded from original query via vocab: [report, create, page, result, pipeline, stage, shell, home, polling, assemble, diagnosis, service]. ReportCreatePage (community HarmonyOS App Shell, src=docs/开发任务包/F3-报告流.md) is the FE create-report page. It is reached from HomePage [EXTRACTED references], then references ReportResultPage [EXTRACTED] which sits in Report Pipeline Stages. The backend hop is ReportCreatePage <--shares_data_with [INFERRED]-- ReportService <--references [EXTRACTED]-- Report Pipeline Skeleton --references [EXTRACTED]--> Stage Protocol (3 hops undirected). ReportResultPage then shares_data_with DimensionResult and Rule-Direct Fallback Copy and references Diagnosis API Contract.
+
+## Outcome
+
+- Signal: useful
+
+## Source Nodes
+
+- ReportCreatePage
+- ReportResultPage
+- HomePage
+- ReportService
+- Report Pipeline Skeleton
+- Stage Protocol
+- Report Task Polling

graphify-out/memory/query_20260815_094511_how_do_the_four_stage_protocol_stages_fill_dimensi.md

@@ -0,0 +1,31 @@
+---
+type: "query"
+date: "2026-08-15T09:45:11.015591+00:00"
+question: "How do the four Stage Protocol stages fill DimensionResult?"
+contributor: "graphify"
+outcome: "useful"
+source_nodes: ["Stage Protocol", "assemble_stages", "VisionStage", "DiagnosisStage", "CopyStage", "ValidationStage", "DimensionResult", "ReportContext", "Report Pipeline Skeleton", "derived_features"]
+---
+
+# Q: How do the four Stage Protocol stages fill DimensionResult?
+
+## Answer
+
+Expanded via vocab: [stage, protocol, assemble, vision, diagnosis, copy, validation, dimension, result, pipeline, skeleton, context, provider, fallback, rule]. Report Pipeline Skeleton references assemble_stages which wires VisionStage, DiagnosisStage, CopyStage, ValidationStage; all four implement Stage Protocol and share ReportContext. VisionStage writes derived_features via VisionProvider. DiagnosisStage fills DimensionResult using DIMENSIONS 32-Spec Dictionary, evaluate RuleVerdict, and kb_color Palette. CopyStage reads ReportContext and DimensionResult then hands to ValidationStage. ValidationStage checks PEJORATIVE_TERMS and can use Rule-Direct Fallback Copy. ReportResultPage consumes DimensionResult and fallback copy. Path VisionStage to DimensionResult is 3 hops via assemble_stages and DiagnosisStage.
+
+## Outcome
+
+- Signal: useful
+
+## Source Nodes
+
+- Stage Protocol
+- assemble_stages
+- VisionStage
+- DiagnosisStage
+- CopyStage
+- ValidationStage
+- DimensionResult
+- ReportContext
+- Report Pipeline Skeleton
+- derived_features