Skip to content

ecosystem: refresh the readiness evidence of the agentskit product - #2018

Open
noxcode-factory[bot] wants to merge 6 commits into
mainfrom
factory/agentskit-io-agentskit-1891
Open

noxcode-factory[bot] wants to merge 6 commits into
mainfrom
factory/agentskit-io-agentskit-1891

Conversation

@noxcode-factory

@noxcode-factory noxcode-factory Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Refs #1891
Linear: AGE-2221

Opened by the factory line (run gh:AgentsKit-io/agentskit#1891, requested by @EmersonBraun).

Agent notes

Agent notes

Refs #1891

I re-ran the gates on the merged head (origin/main has no newer commits) on 2026-11-16 and again on 2026-11-17. Gates that fail stay fail or blocked and have a remediation. The host has no browser, so seo and accessibility are blocked (they could not run). Severities use the schema values (p1/p2/info).

Done-when

  • No evidence-freshness finding for agentskit — proof: ecosystem-readiness/evidence/agentskit.json has auditedOn 2026-11-16 and 12 gates. In artifacts/ecosystem-readiness/latest.md, agentskit's findings are only its own gate records (quickstart fail/p1; documentation fail/p2; seo, accessibility, security, maturity blocked/p2). There is no evidence-valid and no evidence-freshness finding for it.
  • pnpm test:ecosystem-readiness passes — proof: 9 passed (re-run after 67d95b7d). scripts/ecosystem-readiness.test.mjs asserts no evidence-valid finding, no evidence-freshness finding, auditedOn and full gate coverage.
  • Commit docs(ecosystem): refresh agentskit readiness evidence — proof: c8951e7 (follow-ups 1c1d97b, da5ed6c, 67d95b7d).
  • Gates still failing or unable to run, which is what is left: quickstart (2 failures in scripts/reference-docs-vertical.test.mjs), documentation ('ecosystem documentation quality contract': re-attest docs/evidence/ecosystem-documentation-quality/agentskit.json), seo and accessibility (no browser on the host), and security and maturity (they wait for a green quality-gates run). Fix these and re-audit on a host with a browser.

Reviewer return items (this round)

  • documentation gate records the real result — done: in ecosystem-readiness/evidence/agentskit.json, documentation is status fail, severity p2. Its summary names the 'ecosystem documentation quality contract' gate (certified llms.txt drifted from attested commit f69eddb, which is not an ancestor of HEAD). The command is pnpm check:quality-gates and the remediation is to re-attest. latest.md:57 shows P2 agentskit / documentation (fail).
  • performance and links summaries match the run — done: a pnpm check:quality-gates run on HEAD on 2026-11-17 printed Content pipeline — PASS (3 recipe(s)) and nested ternary gate passed against origin/main, and ended with ✗ 1 gate(s) failed: ecosystem documentation quality contract. So performance and links are now pass/info and no longer name recipe factory or content pipeline. The security and maturity summaries (still blocked) now name only that gate.
  • Re-ran pnpm report:ecosystem-readiness and pnpm docs:bridge:index — done: artifacts/ecosystem-readiness/latest.{json,md} and .doc-bridge/{index,capabilities}.json are committed in 67d95b7d.
  • Notes match the committed evidence — done: this file.

Earlier return items (kept)

  • Severities high/medium replaced with allowed values — done (1c1d97b).
  • doc-bridge and llms gate records match a real run — done: after pnpm docs:bridge:index, pnpm docs:bridge:gate exits 0, and llms.txt is unchanged by the regen.
  • Is the "ecosystem documentation quality contract" failure new against base? — no, it is pre-existing. f69eddb is not an ancestor of main, and the certified path llms.txt differs from it at both origin/main and HEAD. This PR touches none of the certified paths.

Validation

  • pnpm check:quality-gates → exit 1, only "ecosystem documentation quality contract" (pre-existing on main)
  • pnpm test:ecosystem-readiness → 9 passed
  • pnpm test:reference-docs → 2 failed | 10 passed (recorded as quickstart fail)
  • pnpm docs:bridge:gate → exit 0; pnpm docs:build → exit 0

Rubric

  • Criterion 1 (no freshness finding) — survived: auditedOn 2026-11-16 and the manifest parses, so freshness is evaluated. latest.md has no freshness finding for agentskit.
  • Criterion 2 (tests pass) — survived: 9/9, and the guard fails on an invalid manifest.
  • Criterion 3 (commit message) — survived: c8951e7.
  • Refresh is truthful — survived: every gate record matches the 2026-11-17 quality-gates run (see above).
  • No secrets, CI weakening, stray files or private content — survived: the diff touches only evidence, generated artifacts, .doc-bridge and one test.

Change rule: sem mudança de comportamento (evidence/docs/test only).

Factory-Line and others added 3 commits October 29, 2026 04:36
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Regenerated deterministic knowledge, site and ecosystem stats snapshots.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

URL Performance Accessibility Best practices SEO
http://127.0.0.1:3000/ 63 100 100 100
http://127.0.0.1:3000/docs 85 100 100 100
http://127.0.0.1:3000/docs/get-started/getting-started/quickstart 86 100 100 100
http://127.0.0.1:3000/stack 96 100 100 100
http://127.0.0.1:3000/showcase 94 100 100 100

Run by .github/workflows/lighthouse.yml.

@noxcode-factory
noxcode-factory Bot marked this pull request as ready for review November 16, 2026 17:00
Factory-Line and others added 2 commits November 16, 2026 18:04
Map high->p1 and medium->p2, record the passing docs:bridge:gate run for
the doc-bridge and llms gates, refresh the performance/links summaries and
regenerate the readiness report and Doc Bridge index.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

URL Performance Accessibility Best practices SEO
http://127.0.0.1:3000/ 62 100 100 100
http://127.0.0.1:3000/docs 79 100 100 100
http://127.0.0.1:3000/docs/get-started/getting-started/quickstart 84 100 100 100
http://127.0.0.1:3000/stack 95 100 100 100
http://127.0.0.1:3000/showcase 95 100 100 100

Run by .github/workflows/lighthouse.yml.

@noxcode-factory
noxcode-factory Bot marked this pull request as draft November 16, 2026 18:24
@noxcode-factory
noxcode-factory Bot marked this pull request as ready for review November 16, 2026 18:26
@noxcode-factory
noxcode-factory Bot marked this pull request as draft November 17, 2026 07:59
@noxcode-factory
noxcode-factory Bot marked this pull request as ready for review November 17, 2026 08:00
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

URL Performance Accessibility Best practices SEO
http://127.0.0.1:3000/ 86 100 100 100
http://127.0.0.1:3000/docs 84 100 100 100
http://127.0.0.1:3000/docs/get-started/getting-started/quickstart 83 100 100 100
http://127.0.0.1:3000/stack 96 100 100 100
http://127.0.0.1:3000/showcase 96 100 100 100

Run by .github/workflows/lighthouse.yml.

@noxcode-factory
noxcode-factory Bot marked this pull request as draft November 17, 2026 09:06
@noxcode-factory
noxcode-factory Bot marked this pull request as ready for review November 17, 2026 09:07
@noxcode-factory

Copy link
Copy Markdown
Contributor Author

Factory line: delivered — waiting for approval. The PR is green and reviewed at head 54a7cff; the repository's rule requires a person's approval (405: Repository rule violations found

New changes require approval from someone other than the last pusher.

). It is in the Decisions lane of the App (no release). The merge train merges it when a person approves this head. The line already freed the slot: there is no new round and no new attempt.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant