chore(main): release engine-and-dependents libraries

[JSONbored]

🤖 I have created a release beep boop

contract: 3.18.4

3.18.4 (2026-07-31)

Fixes

• mcp: compare property schemas in checkInputNarrowing (#10124) (f8fe08d)

engine: 3.18.4

3.18.4 (2026-07-31)

Fixes

• engine: correct the iterate-policy ceiling field docs to match the real precedence (#10131) (98a2564), closes #9997
• engine: count fnmatch label-pattern wildcard groups per raw star, not by path-glob rules (#10128) (1d2b142), closes #9994
• engine: reject over-complex screenshotTableGate whenPaths globs at normalization (#10115) (afe6969), closes #9993

mcp: 3.18.4

3.18.4 (2026-07-31)

Chores

• mcp: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/contract bumped from ^3.18.3 to ^3.18.4
    • @loopover/engine bumped from ^3.18.3 to ^3.18.4

miner: 3.18.4

3.18.4 (2026-07-31)

Chores

• miner: Synchronize engine-and-dependents versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @loopover/contract bumped from ^3.18.3 to ^3.18.4
    • @loopover/engine bumped from ^3.18.3 to ^3.18.4

---

This PR was generated with Release Please. See documentation.

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-31 09:19:02 UTC}

12 files · 1 AI reviewer · 1 blocker · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is an automated release-please version-bump PR: it bumps contract/mcp/miner/engine from 3.18.3 to 3.19.0 in lockstep across package.json files, the release manifest, server.json, expected-engine.version, package-lock.json, and appends the corresponding CHANGELOG entries. All version/dependency references are updated consistently (e.g. loopover-mcp and loopover-miner both bump their @​loopover/contract and @​loopover/engine deps to ^3.19.0, matching package-lock.json), and expected-engine.version is kept in sync with the engine bump. The diff is exactly what a release-please chore PR should contain, with no hand-written logic changes.

Nits — 5 non-blocking

• The 'no published SLSA/sigstore attestation' and 'no verifiable CI pipeline' flags in the external brief are boilerplate supply-chain noise for a first-party monorepo release PR and not actionable here.
• package-lock.json's line count flagged as a 'long file' is expected and unavoidable for a lockfile update — not a real concern.
• Verify expected-engine.version (3.19.0) matches the actual @​loopover/engine version the miner package.json now depends on (^3.19.0), which it does here — good consistency to keep enforcing in future release PRs.
• Diff looks like trivial or whitespace-only churn — Reduce whitespace-only or formatting-only churn and keep the diff focused on substantive changes.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Concerns raised — review before merging

• No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected: No closing reference or linked issue number was found in the PR metadata/body. — If this PR is intended to solve an issue, link it explicitly in the PR body.

Decision drivers

• ❌ Code review — 1 blocker (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
Related work	⚠️ 2 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	⚠️ 12/25	Preflight needs author follow-up before maintainer review.
Contributor workload	✅ 10/10	Author activity: 9 registered-repo PR(s), 8 merged, 332 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 9 PR(s), 332 issue(s).
Improvement	ℹ️ Insufficient signal	risk: low · value: insufficient-signal

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, MDX, Shell, Solidity, JavaScript
• Official Gittensor activity: 9 PR(s), 332 issue(s).
• Related work: Titles/paths share 6 meaningful terms. (PR #10134)
• Related work: Titles/paths share 2 meaningful terms. (issue #9102)

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 4 steps in the Signals table above.

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.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Decision record

• action: hold · clause: missing_linked_issue
• config: 5494cefef7033a8f6999c0369b39fba0b787ce11d0345929429686e6f4565bbb · pack: oss-anti-slop · ci: passed
• record: 5a02fe038ccca19bfd785cd75242ee67206fe6d97aa4a56668ef8123a0979aa2 (schema v6, head 6a137d4)

_{🟩 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 LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.99%. Comparing base (98a2564) to head (55a5e6c).
⚠️ Report is 4 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #10122   +/-   ##
=======================================
  Coverage   91.99%   91.99%           
=======================================
  Files         931      931           
  Lines      114000   114000           
  Branches    27523    27523           
=======================================
  Hits       104877   104877           
  Misses       7823     7823           
  Partials     1300     1300           

Flag	Coverage Δ
backend	95.67% <ø> (ø)
engine	72.99% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
🔵 In progress View logs	loopover-ui	c9eba2b	Jul 31 2026, 08:44 AM

[superagent-security]

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