From b187af5282f6dc8165f3bcb0738bffedb3e14e51 Mon Sep 17 00:00:00 2001 From: graphlemon Date: Thu, 6 Aug 2026 18:15:48 +0800 Subject: [PATCH] graphlemon: auto-commit uncommitted changes for prd-consistency-34bca1cd4d41 --- .claude/agent-memory/planner/MEMORY.md | 1 + .claude/agent-memory/planner/project_nav_current_project_context_prd.md | 31 +++++++++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 0 deletions(-) create mode 100644 .claude/agent-memory/planner/project_nav_current_project_context_prd.md diff --git a/.claude/agent-memory/planner/MEMORY.md b/.claude/agent-memory/planner/MEMORY.md index 5203846..39cc9d4 100644 --- a/.claude/agent-memory/planner/MEMORY.md +++ b/.claude/agent-memory/planner/MEMORY.md @@ -5,3 +5,4 @@ - [artifact overview click-through bug: RESOLVED](project_artifact_overview_click_through_bug.md) — re-verified 2026-08-06, all 3 gaps fixed (data-artifact-id, #/artifacts/:id route, mountArtifactBrowser seeding); re-check before trusting "resolved" long-term - [org-strip click-through bug: 3 render sites, not 1](project_org_strip_click_through_bug.md) — renderOrgStrip (dashboard), v_task_detail's inline org-strip, and #/graph's renderOrgGraphTopology all share the same no-click gap; DAG/log/artifact display mechanisms already exist and must be reused, not rebuilt; no new backend endpoint needed - [run-history click → missing run detail page](project_run_history_click_missing_detail_page.md) — gc_runs_list click only switches task selector, no #/runs/:run_id route exists (documented trade-off, not a bug regression); DAG-panel+log-viewer funcs are run-object-generic and reusable verbatim; backend needs one new by-run_id query since _work_nodes_for_run already exists keyed by run_id +- [nav current-project-context PRD: consistent](project_nav_current_project_context_prd.md) — reviewed 2026-08-06, no contradictions; FR-5's "query-string parsing fix" is actually an add (render() has no query-string parsing today, only hash-path regex) — flag as accuracy issue at SDD stage, not a PRD contradiction diff --git a/.claude/agent-memory/planner/project_nav_current_project_context_prd.md b/.claude/agent-memory/planner/project_nav_current_project_context_prd.md new file mode 100644 index 0000000..e41407c --- /dev/null +++ b/.claude/agent-memory/planner/project_nav_current_project_context_prd.md @@ -0,0 +1,31 @@ +--- +name: project-nav-current-project-context-prd +description: PRD "导航栏『当前项目』上下文（项目名+任务状态摘要）" reviewed 2026-08-06 for internal contradictions — none found +metadata: + type: project +--- + +Reviewed the Planner-stage PRD titled "导航栏『当前项目』上下文（项目名 + 任务状态摘要）" +(nav bar current-project display FR-1/2, clickable task-status-count summary FR-3/4, +query-string parsing fix in `frontend/app.js`'s `render()` FR-5, refresh-on-route-change +FR-6; explicitly scoped out a new backend aggregation endpoint and nav-bar WebSocket live +refresh) for internally contradictory requirements. Found none — the backend-endpoint +scope-out is reasoned (existing no-pagination precedent + documented revisit threshold) +and the route-change-only refresh (FR-6) doesn't conflict with skipping WebSocket live +refresh (discrete-refresh vs push-refresh are different, compatible mechanisms). + +**Why:** worth recording because a sibling PRD in the same pipeline (the `v_graph_console` +Graph page PRD, see `frontend/.graphlemon/runs/7400d876-a797-4d87-bcff-4e59a3befba1/prd.md`) +*did* have a real self-contradiction in its v1 draft (claimed both "shared render code with +v_task_detail" and "v_task_detail's click behavior unaffected" with no reconciliation +mechanism) that got caught by this same consistency-review step and fixed in v2 via an +opt-in `enableNodeClick` parameter — so this check is not pro forma, it has caught a real +issue before in this codebase. + +**How to apply:** existing baseline in `docs/sdd/02-V-界面与交互.md` §nav only documents +"当前项目名 + 切换项目链接" — no task-status-count summary yet. That's an SDD gap this PRD +fills, not a contradiction. If this PRD proceeds to SDD stage, `frontend/app.js`'s actual +`render()` (line 118) only does hash-*path* regex routing (`TASK_DETAIL_RE` etc.) — no +query-string (`?key=value`) parsing exists there at all today, so FR-5 ("fix") is really +"add"; flag that wording precisely if it recurs at SDD/Coder stage (accuracy issue, not a +contradiction, so it wasn't in-scope for this consistency review). -- libgit2 0.21.4