Skip to content

fix(docs): use Gittensor screenshot in homepage hero - #11

Merged
JSONbored merged 1 commit into
mainfrom
codex/docs-hero-screenshot-release-audit
May 26, 2026
Merged

fix(docs): use Gittensor screenshot in homepage hero#11
JSONbored merged 1 commit into
mainfrom
codex/docs-hero-screenshot-release-audit

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • moves the real Gittensor screenshot into the homepage hero and removes the generic logo-art hero image
  • adds more top spacing and tightens the homepage hero type scale
  • updates the MCP publish workflow so future package tags create/update a GitHub Release after npm trusted publishing

What changed

  • uses /images/gittensor-home-signal.webp as the VitePress homepage hero image
  • removes the duplicated lower screenshot block and simplifies the lower context copy
  • adjusts desktop/mobile hero spacing, image sizing, and headline scale
  • grants the publish workflow contents: write so it can create GitHub Releases for mcp-v* tags
  • adds an idempotent release creation/edit step after the npm publish step
  • refreshes root and MCP changelogs

Why

The previous page still had the screenshot buried near the bottom, used unrelated logo art in the hero, and sat too close to the navbar. The package release also had a tag but no GitHub Release, so the repo sidebar did not show a release version.

Validation

  • npm run test:ci

Notes

  • @jsonbored/gittensory-mcp@0.1.4 already has npm provenance attestation.
  • GitHub Packages sidebar remains empty unless we intentionally publish a duplicate package to GitHub Packages; npm registry packages do not show there.

@JSONbored
JSONbored merged commit 217c36a into main May 26, 2026
1 check passed
@JSONbored
JSONbored deleted the codex/docs-hero-screenshot-release-audit branch May 26, 2026 17:24
@JSONbored JSONbored added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jun 10, 2026
JSONbored added a commit that referenced this pull request Jun 26, 2026
…ecks via changedPaths (#1413)

Part two of the predict_gate parity work (#11-13/#18). The oracle now accepts the
PR's changed file PATHS (metadata only — paths, never source content, so the
predictor stays metadata-only) and, when supplied, evaluates the path-dependent
gates the live gate enforces:
 - ALL review.pre_merge_checks (path-gated ones now match their whenPaths), not
   just the path-independent subset.
 - the focus-manifest path policy (manifest_blocked_path / _linked_issue_required /
   _missing_tests), threaded through manifestPolicyGateMode so block-mode blocks.

The slop score stays disclaimed: it needs the diff CONTENT, which a metadata-only
oracle must never receive — so #13 is resolved by design, not by adding a gate.
The note is now conditional: with paths it disclaims only slop; without them it
also discloses the path-policy/path-gated gap.

Wiring: the API route already accepted changedFiles (no schema change); the MCP
tool gains an optional changedPaths field. No output-schema change → no OpenAPI
regen.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant