Frontmatter
| title | docs(release): add v13 evaluation CTA (#12797) |
| author | neo-gpt |
| state | Merged |
| createdAt | Jun 9, 2026, 1:59 AM |
| updatedAt | Jun 21, 2026, 3:46 PM |
| closedAt | Jun 9, 2026, 3:24 AM |
| mergedAt | Jun 9, 2026, 3:24 AM |
| branches | dev ← agent/sync-12797-v13-evaluation-cta |
| url | https://github.com/neomjs/neo/pull/12798 |
| contentTrust | |
| projected | |
| quarantined | 1 |
| signals | [] |
Merged
github-actions
commented on Jun 9, 2026, 2:00 AM
🚨 Agent PR Body Lint Violation
@neo-gpt — your PR body on PR #12798 [QUARANTINED_URL: github.com] does not match the pull-request template structure.
Required action: read .agents/skills/pull-request/SKILL.md BEFORE editing the PR body. The skill points at:
- Minimum-viable PR body structure:
.agents/skills/pull-request/references/pull-request-workflow.md §9 - Self-Identification mandate:
.agents/skills/pull-request/references/pull-request-workflow.md §5
Do NOT compose a substitute template or hallucinate section headings. The validator checks more structural anchors than this comment names. The only reliable path to passing is reading the actual workflow file and following its structure.
Diagnostic hint: at least one recognized anchor like Evidence: is missing.
Visible anchors missing (full list)
Evidence:## Test Evidence## Post-Merge Validation
This is the CI tool-boundary lint companion to PR #11494's MCP manage_pr_review validator and PR #11502's agent-pr-review-body-lint.yml reviewer-side lint.
Resolves #11501.
tobiu
APPROVED reviewed on Jun 9, 2026, 3:24 AM
No review body provided.
Authored by GPT-5 Codex (Codex Desktop). Session 720fc09a-e8ff-467d-b039-28120312964d.
Resolves #12797 Related: #12696, #12577, #12587
Adds a compact
Evaluate It Without Rewriting Your Stacksection to the v13 release notes. The new CTA frames adoption as a low-risk shadow PoC, points to public deployment and ingestion docs, and routes questions or ideas through GitHub, Discord, and Slack without inventing commercial support promises or naming private deployments.Evidence: L1 (static release-note/source-link audit) → L1 required (documentation CTA with public proof/link checks). No residuals.
Deltas from ticket
No scope additions. The implementation stayed inside
resources/content/release-notes/v13.0.0.md; README, portal CTA copy, generated SEO output, and business-owned service/contact copy remain out of scope.ACTIONS touched: yes. Changed CTA-bearing surface:
resources/content/release-notes/v13.0.0.md. Referenced-but-unchanged surfaces:README.mdCommunity links and public deployment-guide links. Audience: CTO / architect / engineering-lead evaluator. Door types: learn, proof, community, contribute.Business/product boundary: no SLA, 24/7 support, pricing, lead-capture, enterprise-relations, advisory-board, or commercial-support copy added. No private organization, private deployment, private business target, or confidential usage detail named.
Test Evidence
ask_knowledge_base(...)attempted for release-note CTA context; KB unavailable, so live repo/GitHub evidence was used instead.README.mdsource read confirms Discord and Slack community links.learn/benefits/DeployingTheAgentOS.md,learn/agentos/cloud-deployment/Day0Tutorial.md,learn/agentos/cloud-deployment/TenantIngestionModel.md.rg -n "the tenant|SLA|24/7|enterprise relations|advisory board|pricing|commercial support" resources/content/release-notes/v13.0.0.md -Sreturned no matches.git diff --checknode ./buildScripts/util/check-whitespace.mjsgit diff --cached --checkmerge-base HEAD origin/dev == origin/dev.Post-Merge Validation
Commits
3ddc39b99— add v13 evaluation CTA.Review Routing
Cross-family review is required because this touches a CTA identity surface. I will request one primary cross-family reviewer after current-head CI is green.