feat(analytics): CPM critical-path engine — pure + tested (slice 6a, stacked on #217)#218
Merged
Merged
Conversation
Slice 6a: the deepest 공정관리 moat. Pure engine + tests this tick; table/gantt
highlighting follows next.
- analytics.js computeCpm(tasks, {calcDuration?}) — dependency graph from an
optional task.predecessors (array or comma-separated ids → task.id); duration
from task.duration or plannedStart/End day-count (mirrors calculateDurationDays,
or an injected calcDuration). Kahn topo-sort → forward pass (ES/EF), backward
pass (LS/LF), slack=LS-ES, critical=slack≈0. Returns perTask{es,ef,ls,lf,
slack,critical,duration} + projectDurationDays + criticalPath (ordered) +
cycleDetected. Robust to cycles / missing predecessors — never throws.
- Exposed on window.ScopeWeaveAnalytics.computeCpm for the upcoming UI.
- tests/unit/cpm.test.mjs: classic AON example (critical path A→B→D→E, C slack 2,
project 13d), date-based durations, cycle (no throw), empty/ghost-pred.
- package.json test:unit now runs analytics + cpm suites.
app.js untouched (still eval-safe). No new deps.
Stacked on #217.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018LMoqYsUY6usjNMBjvxCbU
This was referenced Jul 5, 2026
Merged
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.
SaaS pivot — slice 6a of N (stacked on #217)
The deepest 공정관리 (schedule-control) moat: a Critical Path Method engine. This tick is the pure engine + tests (low risk); table/gantt critical-path highlighting is the next tick.
analytics.js—computeCpm(tasks, { calcDuration? })task.predecessors(array or comma-separated ids referencingtask.id).task.durationorplannedStart/Endday-count (mirrorscalculateDurationDays; or an injectedcalcDuration).slack = LS−ES,critical = slack≈0.perTask{es,ef,ls,lf,slack,critical,duration}+projectDurationDays+criticalPath(ordered) +cycleDetected.cycleDetected:true(never throws); missing predecessor ids ignored.window.ScopeWeaveAnalytics.computeCpmfor the upcoming UI.Tests (
tests/unit/cpm.test.mjs)duration).cycleDetectedtrue, no critical tasks.Verified
npm run test:unit✓ (analytics + cpm) ·npm run test:api✓ · app.js untouched/eval-safe ✓ · no new deps.🤖 Generated with Claude Code