feat(funnel): surface the earn-on-Gittensor path for oss-anti-slop adopters (#694)

[JSONbored]

What

Completes Pillar 6's funnel (#694): a non-Gittensor adopter running the oss-anti-slop pack now gets a clear opt-in path from "I use the anti-slop gate" → "I'm a Gittensor contributor."

• The predicted-gate verdict gains a funnel field, populated only under the oss-anti-slop pack (null under gittensor — those contributors are already on Gittensor): a public-safe "Gittensor lets GitHub contributors earn for open-source work like this — register to start earning" CTA + the register URL. Reuses GITTENSOR_HOME_URL and the same "earn"-only wording as the existing PR-comment footer.
• Surfaced through the gittensory_predict_gate MCP tool (the agent-native self-check from agent-native pre-submission self-check as a general product #693), so an agent on a non-Gittensor repo sees the conversion path inline with its "will this pass?" answer.

Opt-in + non-spammy: one CTA, oss-anti-slop only, never reward/payout/score wording (public-safe).

Why

The two-sided general product is now complete: maintainer installs the pluggable gate (#692), agent self-checks via MCP (#693), and the adopter has a measurable path to becoming a Gittensor miner (#694). All built on the existing earn-CTA footer + predicted-gate engine.

Tests

• predicted-gate.test.ts: funnel present under oss-anti-slop with the register URL + "earn" copy; null under gittensor; public-safe (no reward/payout/score).
• 97% coverage gate green; workers tests + git diff --check + ui:openapi:check pass.

Closes #694. Completes Pillar 6 (#704: #692/#693/#694 all shipped).

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#713 is no longer open.	No action.

---

💰 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.

[superagent-security]

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

[ghost]

gittensory · advisory review

Reviewed 3 changed file(s) — two independent AI reviewers.

Suggested action: ✅ Safe to merge — both reviewers found no blocking issues.

Reviewer A · gpt-oss-120b — recommends ✅ merge
The PR adds an optional "funnel" field to the predicted gate verdict, exposing a public‑safe earn‑on‑Gittensor message for the oss‑anti‑slop pack, updates the API schema, and adds corresponding tests. The changes respect the public/private sanitizer and appear type‑safe.

Suggestions

• Update any API documentation or OpenAPI specs to include the new funnel field.
• Run the full test suite to ensure no other PredictedGateVerdict constructions are missing the new property.
• Consider marking funnel as z.object({ message: z.string(), registerUrl: z.string() }).optional() in the schema for clearer validation.

Worth double-checking

• Potential TypeScript compile errors in code paths that construct PredictedGateVerdict without the new funnel property.
• Clients consuming the API may need to handle the new optional field.

Reviewer B · nemotron-3-120b-a12b — recommends ✅ merge
The PR adds an opt-in funnel for the oss-anti-slop pack to inform contributors about earning on Gittensor, using public-safe 'earn' wording. It updates the PredictedGateVerdict type, MCP output schema, and includes a test verifying the funnel appears only under oss-anti-slop with appropriate content and absence of forbidden terms. The change respects the public/private boundary and is well-tested.

Suggestions

• Consider replacing z.unknown() with a more specific Zod schema for the funnel field in the MCP output (e.g., z.object({ message: z.string(), registerUrl: z.string().url() }).optional()) for better type safety, though the current approach is consistent with other optional fields in the schema.
• Ensure the GITTENSOR_HOME_URL constant in ../github/footer is verified to be 'https://gittensor.io' (as expected by the test) to avoid configuration drift.

Worth double-checking

• Future changes to the funnel message must continue to avoid forbidden public terms (private context, etc.); the test's regex check helps but relies on vigilance.
• The MCP schema change adds an optional unknown field—low risk but could be made more specific to align with potential future schema improvements.