feat(engine): add hasPlanRunningSteps

[kiannidev]

Summary

• Add hasPlanRunningSteps in @jsonbored/gittensory-engine — returns whether any step in a plan DAG is currently running.
• Pure helper alongside hasPlanPendingSteps, hasPlanFailedSteps, and isPlanFullyCompleted for miner and dashboard status checks.
• Vitest coverage at 100% patch on the new helper.

Test plan

• COVERAGE_NO_THRESHOLDS=1 npx vitest run test/unit/plan-running.test.ts --coverage
• npx diff-cover coverage/lcov.info --compare-branch=main --fail-under=99 → 100%
• npm run build --workspace @jsonbored/gittensory-engine && npm run build:miner

Made with Cursor

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.46%. Comparing base (f5a03bb) to head (ce8e2cd).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3435   +/-   ##
=======================================
  Coverage   93.46%   93.46%           
=======================================
  Files         292      293    +1     
  Lines       30794    30795    +1     
  Branches    11223    11223           
=======================================
+ Hits        28783    28784    +1     
  Misses       1355     1355           
  Partials      656      656           

Files with missing lines	Coverage Δ
packages/gittensory-engine/src/plan-running.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 07:05:24 UTC}

3 files · 1 AI reviewer · no blockers · readiness 55/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This adds a small pure `hasPlanRunningSteps` helper, exports it from the engine barrel, and covers the empty, false, true, and barrel-export paths. The implementation matches the existing plan-status helper pattern and reads directly from `PlanDag.steps`, so the visible diff is correct and low risk. CI already passed on this exact commit, including patch coverage and builds.

Nits — 1 non-blocking

• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (no linked issue context).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 1362 registered-repo PR(s), 668 merged, 49 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kiannidev; Gittensor profile; 1362 PR(s), 49 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: kiannidev
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 1362 PR(s), 49 issue(s).
• Related work: Titles/paths share 10 meaningful terms. (issue #2281, issue #2276)
• Related work: Titles/paths share 8 meaningful terms. (issue #2281, issue #2287)
• Related work: Titles/paths share 8 meaningful terms. (issue #2276, issue #2287)

Contributor next steps

• Explain no-issue PR.
• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.