feat(miner-foundation): scaffold packages/gittensory-engine package skeleton

[GildardoDev]

Summary

Stands up the new shared engine package packages/gittensory-engine/ (@jsonbored/gittensory-engine), packaging-only with no logic moved yet, mirroring the existing packages/gittensory-mcp/ conventions. This is the skeleton that later issues extract deterministic src/ logic into.

Closes #2275

Deliverables

• packages/gittensory-engine/package.json — name @jsonbored/gittensory-engine, version 0.1.0, AGPL-3.0-only, type: module, repository.directory set, publishConfig.access: public, engines.node >=22.0.0, and files scoped to dist + CHANGELOG.md (no src). A real tsc build via main/types/exports pointing at dist.
• packages/gittensory-engine/tsconfig.json — extends the root tsconfig.json so it inherits strict, noUncheckedIndexedAccess, and exactOptionalPropertyTypes, with its own outDir: dist, rootDir: src, and a Node ESM emit (NodeNext) plus declaration.
• packages/gittensory-engine/src/index.ts — placeholder barrel export marking the extraction target for later issues.
• build script (tsc -p tsconfig.json), verified: npm run build --workspace @jsonbored/gittensory-engine emits dist/index.js and dist/index.d.ts.
• Root package.json already globs packages/* in workspaces, so npm ci discovers the package with no additional wiring; the README notes this.
• packages/gittensory-engine/README.md stub explaining the package purpose and independent versioning, plus LICENSE and a CHANGELOG.md stub to match the sibling package layout.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• Packaging-only: no logic moves, no existing files changed. Purely additive under a new package directory.
• Follows CONTRIBUTING.md; does not touch site/, CNAME, or reintroduce removed tooling.
• Linked issue feat(miner-foundation): scaffold packages/gittensory-engine package skeleton #2275.

Validation

• npm run build --workspace @jsonbored/gittensory-engine succeeds and emits dist/ (build artifact, gitignored).
• git diff --check clean.
• No existing file changed; root workspaces auto-discovers the package.

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-01 20:13:18 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
The diff cleanly adds a packaging-only `@​jsonbored/gittensory-engine` workspace with a real `tsc` build, NodeNext package metadata, an empty ESM barrel, README, license, lockfile wiring, and focused scaffold tests for the publish contract. The package shape is internally consistent: entry points target `dist`, `files` excludes source, `tsconfig.json` emits declarations from `src`, and the empty `export {}` keeps the placeholder module buildable. The main maintainership concern is that the PR also hand-edits a package changelog stub, which conflicts with the repo guidance that changelogs are generated rather than edited in ordinary PRs.

Blockers

• packages/gittensory-engine/CHANGELOG.md:1 adds a hand-written changelog in a normal feature PR even though the repo convention says changelogs are generated by release tooling, so remove this file from the PR or point to the existing sibling-package precedent that requires per-package changelogs at scaffold time.

Nits — 7 non-blocking

• test/unit/gittensory-engine-scaffold.test.ts:1 only pins `package.json`; consider adding a small assertion for `tsconfig.json` so the package cannot silently lose `declaration`, `rootDir`, or NodeNext emit settings.
• packages/gittensory-engine/package.json:20 includes forward-looking keywords before any runtime modules exist; keep the metadata minimal unless these are already used by the sibling package convention.
• Remove `packages/gittensory-engine/CHANGELOG.md` from the scaffold, or document the package-specific exception if this package layout intentionally differs from the repo-wide changelog rule.
• Extend `test/unit/gittensory-engine-scaffold.test.ts` to import `packages/gittensory-engine/tsconfig.json` and assert the build contract alongside the package contract.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.
• Pull request duplicates other open work — Check for an existing pull request or issue covering this change and coordinate or consolidate before continuing.
• 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	✅ Linked	#2275
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:M; 1 linked issue).
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: 219 registered-repo PR(s), 161 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	GildardoDev; Gittensor profile; 219 PR(s), 0 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: GildardoDev
• 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: 219 PR(s), 0 issue(s).
• Related work: Titles/paths share 10 meaningful terms. (PR #2389)
• Related work: Titles/paths share 8 meaningful terms. (PR #2378)
• Related work: Titles/paths share 6 meaningful terms. (PR #2392)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Triage stale or unlinked PRs.
• Refresh registry data or choose a registered active repo.
• 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.73%. Comparing base (981355c) to head (ebb9769).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2357   +/-   ##
=======================================
  Coverage   95.73%   95.73%           
=======================================
  Files         223      223           
  Lines       24741    24741           
  Branches     8969     8969           
=======================================
  Hits        23685    23685           
  Misses        433      433           
  Partials      623      623           

🚀 New features to boost your workflow:

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

[superagent-security]

🚨 Contributor flagged. Click here for more info: Superagent Dashboard

[JSONbored]

This is the scaffold, not a normal feature PR. Redact blocker.