feat(projects): PR-PT-1 foundation — reflection field + Projects tab routing + IP detail anatomy prep#172
Merged
Merged
Conversation
…hpad design Resolves Coherence spec §15 carry-forward "IP detail page details — Overview / Sections toggle + team workspace pattern need detailed visual design". Adds new top-level Projects tab (7-tab nav). Improve tab stays as legacy PDCA workbench (zero migration). Home becomes the active-IP launchpad for Project Lead persona; selecting an IP cascades scope to Process / Analyze / Investigation / Improve / Report tabs via the IP-context chip. IP detail page anatomy: stage tabs (Charter / Approach / Sustainment / Handoff) + Overview/Sections segmented toggle + 280px right team rail. Approach stage is SuspectedCause-anchored (per-cause hierarchy: Hypothesis → ImprovementIdea → ActionItem); authoring jumps out to the Improve tab to avoid duplication. Report tab IP-scoped with Overview/Technical audience toggle. Overview renders a 7-section QC-Story-shaped narrative arc (plain-English UI, methodology lineage internal-only per RPS V1 D2). Technical renders the full analytical chart suite (capability histograms, I-Chart with intervention, factor R²adj Pareto, regression scatter, per-cause control charts). Single data-model addition: optional ImprovementProject.reflection?: string field for the analyst's lessons-learned narrative (surfaces in Report Overview "What we standardized + learned" section). Amends Coherence spec §4 (nav) + §15 (carry-forward closure) + §16 (spec contributions matrix). Co-Authored-By: ruflo <ruv@ruv.net>
Applies the §9 amendments described in docs/superpowers/specs/2026-05-14-projects-tab-design.md (committed 2f4cff5) back into the parent coherence spec so the ecosystem stays truthful. Coherence spec amendments: - §4 nav: 6 → 7 tabs (split Improvement → Improve + Projects) + amendment block explaining the deliberate verb/noun split + table updated with separate Improve (PDCA workbench, legacy) and Projects (IP lifecycle, new) rows - §4 prose paragraph for "Improvement" replaced with two paragraphs (Improve = unchanged legacy / Projects = new lifecycle surface) - §15: "IP detail page details" carry-forward marked RESOLVED with link - §16 spec-contributions matrix: new row for the Projects-tab spec Decision-log: - New Replayed Decisions entry 2026-05-14 pinning the six locks (7-tab split / Home active-IP launchpad / IP detail anatomy / SuspectedCause-anchored Approach / Report Overview-Technical with QC-Story arc / reflection field addition) The new Projects-tab spec (2f4cff5) can now cite the coherence spec as up-to-date grounding when implementation plans land. Co-Authored-By: ruflo <ruv@ruv.net>
Plan 1 of 4 covering 5 PRs (PR-PT-1 through PR-PT-5) off branch projects-tab-foundation. Implements docs/superpowers/specs/2026-05-14- projects-tab-design.md D1, D2, D3, D6, D7, D8, D9, D10, D14 + V1 skeleton of D11. Defers D4/D5/D12/D13 + V1 full D11 to Plans 2-4. PR-PT-1 foundation — adds optional ImprovementProject.reflection field, extends panelsStore with 'projects' activeView + selectedProjectId + showProjects action, adds Projects tab button between Improve and Report, renames the existing Improvement label → Improve. PR-PT-2 anatomy — IPDetailHeader + IPDetailStageTabs + IPDetailModeToggle + IPDetailTeamRail skeleton + pure deriveStageState function, all exposed via packages/ui/src/components/IPDetail (new sub-path export). PR-PT-3 Charter — KPI strip + jump-outs + Sections wraps existing form. PR-PT-4 Approach — SuspectedCause-anchored hierarchy via projectCauses pure function + ApproachCauseCard primitive + ApproachOverview/Sections compositions. "Open in Improve workbench" jump-out per cause. PR-PT-5 Sustainment + Handoff — cadence-tick Sustainment Overview + operationalization-checklist Handoff Overview. V1 Sections shims link to legacy Sustainment/Handoff activeView panels. Bite-sized TDD tasks (test fail → implement → test pass → commit) with full code in every step. ~35 tasks across 5 PRs. Spec frontmatter updated to link to the plan (inbound-link requirement). Co-Authored-By: ruflo <ruv@ruv.net>
Per spec D14 — analyst-authored lessons-learned narrative; surfaces in Report Overview "What we standardized + learned" section (Plan 4). Co-Authored-By: ruflo <ruv@ruv.net>
TDD: 3 new tests (red→green). Adds showProjects(projectId?) action, selectedProjectId field, and mirrors 'projects' in useAppPanels activeView union.
Co-Authored-By: ruflo <ruv@ruv.net>
Replace hardcoded indigo-600/700 palette tokens with --vs-accent / --vs-accent-hover CSS variable references to align with the shared theme token system used across the codebase. Co-Authored-By: ruflo <ruv@ruv.net>
…ove label - lazyWithRetry import for ProjectsTabView - projects branch in JSX ternary chain (immediately before improvement) - PhaseId extended with 'projects'; PHASE_TABS adds improve + projects entries - workspace.improve + workspace.projects keys added to MessageCatalog and all 32 locale files Co-Authored-By: ruflo <ruv@ruv.net>
- panelsStore: add 'projects' to activeView union + selectedProjectId field + showProjects action (before 'improvement' in union) - panelsStore tests: reset selectedProjectId in beforeEach + 3 new showProjects tests - ProjectsTabView: create apps/azure/src/components/ProjectsTabView.tsx (verbatim from PWA) - AppHeader: rename 'Improvement' nav label → 'Improve'; add 'Projects' nav button after it - Editor.tsx: import ProjectsTabView + selectedProjectId selector + activeView === 'projects' JSX branch immediately before 'improvement' branch Co-Authored-By: ruflo <ruv@ruv.net>
Co-Authored-By: ruflo <ruv@ruv.net>
…ects (PR-PT-1.5 carry-forward) Co-Authored-By: ruflo <ruv@ruv.net>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jukka-matti
added a commit
that referenced
this pull request
May 14, 2026
…ion' The CATEGORY enum in scripts/docs-frontmatter-schema.mjs doesn't include 'implementation-plan', 'implementation-plan-master', 'implementation-audit', 'chrome-walk', or 'plan'. Schema becomes blocking 2026-05-15 per the frontmatter check; pre-PR-#172 reviewer flagged the drift. Consolidated 17 plan docs to the canonical 'implementation' value (already used by 18 other plan files). Other valid values 'reference' (4) and 'architecture' (1) preserved as-is. Co-Authored-By: ruflo <ruv@ruv.net>
# Conflicts: # docs/superpowers/plans/2026-05-14-projects-tab-foundation.md # docs/superpowers/specs/2026-05-14-projects-tab-design.md
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Plan 1 PR-PT-1 of 5 — foundation for the new Projects tab per
docs/superpowers/specs/2026-05-14-projects-tab-design.mdD1, D2, D3, D14.Changes:
ImprovementProject.reflection?: stringfield (D14, per RPS V1 entity extension)panelsStorewith'projects'activeView +selectedProjectId+showProjects(projectId?)actionuseAppPanels(PWA)ProjectsTabViewcomponent in both PWA + Azure with: empty-state CTA, IP list view, and selected-project placeholder branch (placeholder replaced with<IPDetailPage>in PR-PT-2)workspace.improve+workspace.projectsi18n keys seeded in 32 locales; Azure via hardcoded strings per Azure convention)'improvement'activeView +showImprovementaction untouched (legacyImprovementViewPDCA workbench stays as-shipped per spec D3)Behind: This branch merged
origin/main(commit2944c71c) to pick up PR #169 + PR #171.Test plan
pnpm --filter @variscout/core test— 3403 passedpnpm --filter @variscout/pwa test— 344 passed / 1 skippedpnpm --filter @variscout/azure-app test— 1307 passed (9 pre-existing unrelateduseCanvasViewportLifecycleIndexedDB rejections — confirmed on main)pnpm --filter @variscout/pwa tsc --noEmit— cleanpnpm --filter @variscout/azure-app tsc --noEmit— cleanbash scripts/pr-ready-check.sh— 1 pre-existing failure: Azure vitest exits non-zero due to 9 unhandled DatabaseClosedError (all 1307 tests pass; same on main). Docs frontmatter warning (21 old plan docs) also pre-existing on main.Spec coverage (Plan 1 / PR-PT-1)
reflection?: stringfield addedSubsequent PRs in this plan (PR-PT-2 through PR-PT-5) build the IP detail page on top of this foundation.