feat(engine): parse and coerce MinerGoalSpec from raw config

[kiannidev]

Summary

• Adds parseMinerGoalSpec() — the feat(miner-foundation): MinerGoalSpec type definitions for .gittensory-miner.yml #2293 follow-up parser for .gittensory-miner.yml raw JSON.
• Coerces booleans, path/label lists, floored maxConcurrentClaims, and case-insensitive issueDiscoveryPolicy with warnings on malformed input.
• Returns a deep-frozen spec; exports via @jsonbored/gittensory-engine/miner-goal-spec-parse subpath (avoids index.ts while feat(miner-plan): add analyze and prepare plan-DAG templates to the shared engine #2628 is open).

Scope

• Focused packages/gittensory-engine/ addition with node:test coverage.
• No linked issue — explicit follow-up to feat(miner-foundation): MinerGoalSpec type definitions for .gittensory-miner.yml #2293 type scaffold.

Validation

• npm run build && npx tsc -p tsconfig.test.json && node --test dist-test/miner-goal-spec-parse.test.js — 4/4 passing

Safety

• Pure parser, no IO, no secrets.

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-03 05:33:37 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
The change adds a focused pure parser for the existing MinerGoalSpec shape, wires it through a package subpath export, and covers the main happy and malformed cases. The implementation follows the documented defaults, floors numeric claims, normalizes policy casing, deduplicates trimmed lists, and returns frozen parser output. I do not see a visible correctness break in the changed files, but the malformed-list warning behavior is thinner than the PR description claims.

Nits — 6 non-blocking

• nit: packages/gittensory-engine/src/miner-goal-spec-parse.ts:36 silently drops empty or overlong list entries without a warning, even though the parser otherwise reports malformed input; either warn there too or document that those values are intentionally ignored quietly.
• nit: packages/gittensory-engine/src/miner-goal-spec-parse.ts:59 has no upper bound for maxConcurrentClaims, so a malformed but finite huge number can flow through; consider clamping to a conservative maximum if downstream claim fanout will consume this directly.
• nit: packages/gittensory-engine/test/miner-goal-spec-parse.test.ts:31 only checks wantedPaths is frozen; add blockedPaths/preferredLabels or a mutation assertion if the deep-freeze contract is important.
• In packages/gittensory-engine/test/miner-goal-spec-parse.test.ts, add coverage for non-string list entries plus empty/too-long strings so the warning/drop policy is locked down.
• In packages/gittensory-engine/src/miner-goal-spec-parse.ts, consider extracting the string-list limits into exported or documented constants if callers need to explain rejected config values to users.
• 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 (size label size:L; 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: 1700 registered-repo PR(s), 837 merged, 49 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kiannidev; Gittensor profile; 1700 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: 1700 PR(s), 49 issue(s).
• Related work: Titles/paths share 10 meaningful terms. (issue #2278, issue #2280)
• Related work: Titles/paths share 10 meaningful terms. (issue #2277, issue #2280)
• Related work: Titles/paths share 8 meaningful terms. (issue #2280, issue #2291)

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