feat(ecosystem): o Harness enters in the catalog, between o Doc Bridge e o Playbook - #1617
Merged
Merged
Conversation
Ordem nova: agentskit · registry · chat · doc-bridge · harness · playbook · code-review. Num commit só, porque parcial quebra o teste de contrato: os ids e a ordem são comparados verbatim em vários sítios, e a lista do `ecosystem-contract.mjs` tem de vir primeiro — o `sync-ecosystem.mjs` valida por ela e não corre com um id que não conhece. O "Star on GitHub" da barra passa a seguir o produto onde o visitante está: dar estrela ao AgentsKit a partir do site do Harness é um voto que ninguém quis dar. O `repo` viaja na entrada gerada; sem repositório público, fica a organização. Accent `#F778BA` na forma que os irmãos usam — `dark` e `softLight` espelham o `ecosystem.json`, `light` é a variante mais escura que um fundo claro exige. **O harness fica de fora do programa de qualidade documental**, de propósito. Aquilo é uma certificação auditada com prova por produto; acrescentar um produto novo à lista sem auditoria seria fabricar exatamente a atestação que esses gates existem para impedir. Entra quando alguém o auditar a sério. Os hashes do README Standard foram re-carimbados com as datas de revisão preservadas, e as claims regeneradas. Nota sobre gates: no main limpo falham hoje `verified recipe factory` e `ecosystem documentation quality contract`. Confirmei antes e depois desta alteração — são os mesmos dois, e esta alteração não acrescenta nenhum.
Contributor
Lighthouse
Run by |
Member
Author
|
CI evidence for the one red check, since "it already failed" is a claim worth backing.
The findings name what is drifting, and none of it is in this branch: root README word count (declared 1703, measured 1653), a journey word count, the attestation commit/digest for documentation paths that changed after This branch adds no finding and removes none. Fixing the attestation drift is a separate change — re-stamping a documentation-quality digest to make an unrelated PR green is exactly the fabricated attestation those gates exist to prevent. |
EmersonBraun
changed the title
Contributor
Lighthouse
Run by |
Contributor
Lighthouse
Run by |
Contributor
Lighthouse
Run by |
Contributor
Lighthouse
Run by |
Contributor
Lighthouse
Run by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Harness (
@agentskit/harness,harness.agentskit.io) to the ecosystem, between Doc Bridge andPlaybook. Companion to AgentsKit-io/harness#85, which ships
its 0.15.0 and its documentation site.
New canonical order:
agentskit · registry · agentskit-chat · doc-bridge · harness · playbook · code-review.Why one commit
The ids and their order are compared verbatim in several places, so a partial change fails the contract test.
The order of operations is not free either:
scripts/lib/ecosystem-contract.mjshas to be first, becausesync-ecosystem.mjsvalidates against that list and will not run with an id it does not know.The bar's "Star on GitHub" now follows the current product
Starring AgentsKit from the Harness site is a vote nobody meant to cast.
repotravels with the generatedPROPSentry; a product without a public repository falls back to the organisation.The harness is deliberately not in the documentation-quality programme
That programme is an audited certification with per-product evidence and a content digest. Adding a brand-new
product to its list without an audit would fabricate exactly the attestation those gates exist to prevent. The
catalogue entry does not require it, and the harness joins the programme when someone audits it for real.
Verification
pnpm test:ecosystem— 30/30.node scripts/sync-ecosystem.mjs --check— the three generated files match.node scripts/check-semantic-authority.mjs— passes (its hard-coded product count moved from six to seven).node scripts/check-readme-standard.mjs— passes;readme-standard-v1.jsonhashes re-stamped with--preserve-review-dates, so review dates are untouched.node scripts/gen-ecosystem-claims.mjs --check— the claims and both snapshots are current.pnpm check:quality-gates— failsverified recipe factoryandecosystem documentation quality contract.Both already fail on a pristine
main: I checked outorigin/mainin a separate worktree and got thesame two, before and after this change. This branch adds none.
After merge
www.agentskit.io/ecosystem-bar.jsis what every sibling site loads, so Harness appears in the shared headerand the tour as soon as this deploys — nothing to do in the other repositories.
https://claude.ai/code/session_013RPvGCNrQ9G4RatAgpwbBB