feat(project): add ECC-FE project management and QoR by Luyoung0001 · Pull Request #214 · openecos-projects/ecos-studio

Luyoung0001 · 2026-09-04T07:47:40Z

Summary

Add first-class Project Management support for ECC-FE projects while keeping the existing backend project path behaviorally isolated.

This pull request:

extends the project manifest and lifecycle contracts to distinguish backend and frontend projects;
lets users create, register, import, open, and remove ECC-FE projects and their workspaces through the existing Project Management entry points;
introduces frontend-specific workspace summaries, Dashboard data, Step Analysis, comparisons, attention signals, and project-tree presentation;
adds per-step ECC-FE QoR ingestion and presentation in both the frontend workspace and Project Management views;
refreshes frontend step and QoR state as each stage completes instead of waiting for the entire frontend flow RPC to finish;
recovers interrupted frontend operations when a workspace is reopened;
clarifies QoR scoring, quality gates, hotspots, and reproducibility input snapshots without exposing raw SHA-256 values as user-facing metrics;
updates the ECC-FE gitlink to the merged child implementation at 014e721d87f539ff10cdf167d29010f871009b5e;
refreshes the Agent knowledge source inventories after the backend Project Management module was isolated and renamed.

Architecture

Backend and frontend Project Management remain separate at the behavior layer:

shared manifest and presentation contracts define the common project/workspace surface;
backendProjectManagement.ts retains backend-specific flow and QoR interpretation;
frontend lifecycle and analysis logic lives in dedicated frontend modules and components;
Electron main remains responsible for project-scoped filesystem reads, runtime recovery, and IPC validation;
the renderer consumes validated project data without receiving unrestricted filesystem access.

The goal is visual and workflow consistency without coupling ECC-FE semantics to the backend RTL-to-GDS implementation.

Frontend Project Lifecycle

Add frontend-aware project manifest parsing, validation, and registration.
Add Backend/Frontend selection to New Project.
Reuse the ECC-FE workspace wizard when creating frontend project workspaces.
Support project creation, import, open, history registration, and deletion.
Preserve project and workspace scope checks at the Electron boundary.
Restore frontend workspace sessions and recover interrupted operations when reopening a project workspace.

Dashboard And Analysis

Build frontend workspace summaries from ECC-FE artifacts and flow state.
Add frontend Dashboard, workspace comparison, Needs Attention, and Step Analysis data.
Keep project-tree rows, analysis frames, typography, widths, and scrolling consistent with the backend Project Management surface.
Keep frontend analysis rendering in dedicated components so backend behavior is not changed.
Harden missing, malformed, and partially available workspace artifact handling.

Frontend QoR

Parse ECC-FE QoR metrics, summaries, hotspots, gates, and step status.
Show QoR inside the active frontend workspace as well as Project Management.
Refresh QoR immediately when each frontend stage completes.
Hydrate already completed stages from persisted local artifacts.
Add readable per-stage score breakdowns and scoring explanations.
Add scrollable hotspot/report areas for long analysis output.
Replace ambiguous expressions such as 0 == 0 with user-facing gate descriptions.
Present reproducibility inputs as an Input Snapshot, with validated tracking state and concise source/configuration context.

Scope

Select the areas touched by this PR:

GUI - desktop UI/runtime changes in ecos/gui, including renderer, Electron, and shared packages.
ECC - ECC submodule updates or ECOS Studio integration with the ECC CLI/runtime.
Resource management - resource registry, downloads, installation, manifests, PDKs, or tool assets.
Build, packaging, Nix, or release workflow - build inputs, AppImage packaging, or release metadata.
CI - GitHub Actions workflows, reusable actions, triggers, path filters, or automated checks.
Documentation only - README, guides, templates, or docs with no runtime behavior change.

Validation

Manual GUI verification covered frontend project creation/opening, frontend workspace rendering, project tree expansion, Dashboard and Step Analysis presentation, per-stage flow/QoR refresh, persisted QoR hydration, recovery on workspace reopen, scrolling, and layout alignment.

Skipped checks and reason:

pnpm run build, make build, and demo targets were not run because this change does not modify packaging scripts, native build inputs, or demo definitions; platform packaging remains covered by PR CI.
The full Agent suite reached 104 passing tests with one pre-existing non-deterministic assertion that requires generated CTS prose to contain the exact English token clock-tree; valid CTS/Chinese responses can omit that literal. The knowledge generator check itself passes.

Screenshots or Recordings

No recording is attached. The affected GUI workflows were exercised manually during implementation, including frontend project lifecycle, Dashboard, Step Analysis, QoR updates, and layout behavior.

Release, Packaging, and Runtime Impact

No release, packaging, or runtime impact
Version metadata changed
AppImage or Electron packaging changed
ECC CLI runtime resources changed
OSS CAD Suite, PDK, resource download, or installer behavior changed
Submodule gitlink changed

Notes:

ECC-FE advances to 014e721d87f539ff10cdf167d29010f871009b5e, which is already merged into openecos-projects/ecc-fe:main.
No dependency lockfile or release-version change is included.
Backend Project Management behavior is intentionally preserved while frontend behavior is implemented through separate adapters, readers, analysis modules, and views.

Checklist

I kept the change scoped to the affected component.
I updated docs or user-facing text where behavior changed.
No dependency changes required lockfile updates.
I documented intentional submodule updates.
I did not include local caches, virtual environments, or generated build outputs.
I explained skipped validation and remaining risk.

…anagement

Add the shared analysis frame and frontend project dashboard. Keep backend and frontend panels decoupled. Scope workspace actions to their owning project and preserve explicit workspace selection across project changes.

# Conflicts: # ecos/agent/knowledge/cts/manifest.json # ecos/agent/knowledge/cts/sources.json # ecos/agent/knowledge/drc/manifest.json # ecos/agent/knowledge/drc/sources.json # ecos/agent/knowledge/filler/manifest.json # ecos/agent/knowledge/filler/sources.json # ecos/agent/knowledge/fixfanout/manifest.json # ecos/agent/knowledge/fixfanout/sources.json # ecos/agent/knowledge/floorplan/manifest.json # ecos/agent/knowledge/floorplan/sources.json # ecos/agent/knowledge/harden/manifest.json # ecos/agent/knowledge/harden/sources.json # ecos/agent/knowledge/legalization/manifest.json # ecos/agent/knowledge/legalization/sources.json # ecos/agent/knowledge/place/manifest.json # ecos/agent/knowledge/place/sources.json # ecos/agent/knowledge/rcx/manifest.json # ecos/agent/knowledge/rcx/sources.json # ecos/agent/knowledge/route/manifest.json # ecos/agent/knowledge/route/sources.json # ecos/agent/knowledge/sta/manifest.json # ecos/agent/knowledge/sta/sources.json # ecos/agent/knowledge/synthesis/manifest.json # ecos/agent/knowledge/synthesis/sources.json # ecos/gui/apps/desktop-electron/electron/services/projectManagementReadService.ts # ecos/gui/apps/renderer/src/components/NewProjectWizard.vue # ecos/gui/apps/renderer/src/types/index.ts # ecos/gui/apps/renderer/src/utils/backendProjectManagement.ts # ecos/gui/packages/shared/src/index.ts # ecos/gui/packages/shared/src/types/workspace.ts # ecos/gui/packages/shared/src/utils/projectManagementSummary.test.ts # ecos/gui/packages/shared/src/utils/projectManagementSummary.ts # ecos/gui/packages/shared/src/utils/projectManifest.ts

…anagement # Conflicts: # ecos/gui/apps/desktop-electron/electron/services/chipViewerService.test.ts

Emin017 · 2026-09-09T08:27:03Z

@@ -1 +1 @@
-Subproject commit fefb988b771b407d551daeabde2005abb3349536
+Subproject commit 687c28e18ce648864b1ca6fc3a56527c2674fe1a


[P1] Delay runtime activation until required resources install

docs/ecc-fe-cli-setup.sh writes the active manifest and replaces both command links before running resource install --required. If a required resource download, verification, or installation fails, set -e exits with this failed runtime still active; an upgrade also stops pointing users at the previously working runtime. Please commit the manifest and links only after all required resources succeed, or roll them back on failure, so a failed first install leaves no active runtime and a failed upgrade preserves the prior one.

Emin017 · 2026-09-09T08:27:03Z

+          workspace.workspace_id,
+          {
+            analysis: {
+              frontendDetailTexts: Object.fromEntries(


[P2] Preserve unavailable frontend artifact state

The read service returns null and records the path in unavailablePaths when a detail file exceeds the 1 MiB limit or another read error occurs, but this mapping discards that status. If flow.json still says the step succeeded, downstream analysis turns the missing detail into zero errors, warnings, and cases, producing a false-green dashboard. Please propagate the unavailable state and render these aggregates as unknown instead of successful zero-result data.

Luyoung0001 added 27 commits August 20, 2026 11:19

refactor(project): add frontend-aware manifest core

6727976

refactor(gui): isolate project workspace readers

f77faec

refactor(gui): isolate backend project model

17af8c7

fix(gui): preserve project flow state semantics

78df995

Merge remote-tracking branch 'origin/main' into feat/ecc-fe-project-m…

84c3fb6

…anagement

feat(project): add frontend project lifecycle

202b64a

feat(project): read frontend workspace summaries

9b76cfb

feat(project): add frontend analysis dashboard

fb78e8f

chore: update ecc-fe submodule

f3a647c

fix(project-management): harden frontend workspace analysis

73d1190

fix(agent): align audited knowledge source paths

07127ee

feat(project-management): align frontend analysis surface

4e68915

Add the shared analysis frame and frontend project dashboard. Keep backend and frontend panels decoupled. Scope workspace actions to their owning project and preserve explicit workspace selection across project changes.

fix(project-management): restore initial page mount

f145c61

fix(project-management): align project tree rows

5c0dd6d

fix(gui): recover interrupted frontend operations

988dea3

chore: update ecc-fe submodule

54f99e1

feat(gui): add frontend QoR analysis

f8873ec

fix(gui): refresh frontend QoR per completed step

b1c1e0f

fix(gui): hydrate frontend QoR from local artifacts

34ab4d2

feat(gui): explain frontend QoR scoring

2cda0b9

chore: update ecc-fe submodule

c6fc6fe

fix(gui): stabilize frontend analysis layout

03d47fe

Merge origin/main into feat/ecc-fe-project-management

d8f42cc

fix(gui): clarify frontend QoR input snapshots

4a3d358

chore: update ecc-fe submodule

a9aaa09

fix(agent): refresh project management knowledge sources

849c627

Luyoung0001 requested a review from Emin017 September 4, 2026 07:51

Luyoung0001 added 2 commits September 4, 2026 17:59

Merge remote-tracking branch 'origin/main' into feat/ecc-fe-project-m…

e1da057

…anagement # Conflicts: # ecos/gui/apps/desktop-electron/electron/services/chipViewerService.test.ts

chore: update ecc-fe submodule

7e3c264

Luyoung0001 added 2 commits September 8, 2026 14:36

chore: update ecc-fe submodule

eaba1e6

chore: update ecc-fe submodule

4ef6626

Emin017 reviewed Sep 9, 2026

View reviewed changes

Luyoung0001 added 3 commits September 10, 2026 10:39

feat(projects): clarify project and workspace creation

a476f95

chore: update ecc-fe submodule

f8509d6

fix(project): preserve unavailable frontend artifacts

cdf1b19

Navigation Menu

Uh oh!

feat(project): add ECC-FE project management and QoR - #214

feat(project): add ECC-FE project management and QoR#214
Luyoung0001 wants to merge 34 commits into
mainfrom
feat/ecc-fe-project-management

Luyoung0001 commented Sep 4, 2026

Uh oh!

Emin017 Sep 9, 2026

Uh oh!

Emin017 Sep 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -1 +1 @@
		Subproject commit fefb988b771b407d551daeabde2005abb3349536
		Subproject commit 687c28e18ce648864b1ca6fc3a56527c2674fe1a

Uh oh!

Conversation

Luyoung0001 commented Sep 4, 2026

Summary

Architecture

Frontend Project Lifecycle

Dashboard And Analysis

Frontend QoR

Scope

Validation

Screenshots or Recordings

Release, Packaging, and Runtime Impact

Checklist

Uh oh!

Emin017 Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

Emin017 Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants