docs: refresh portfolio register and status snapshot for 2026-08-28 - #60
Merged
Conversation
Record the 2026-08-25 maintainer merge batch across all repositories, the open feature pull requests (#59, #33, #30, #17, #14, #19, #16), the current main-branch CI runs on c9d11cb, and add agentsmd as the fifth registered repository with its outside fork recorded as a lead, not usage. Supersedes the 2026-08-24 register.
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.
What
Refresh the operating status documentation to the verified live signals of
2026-08-28:
covering five repositories (adds
agentsmd, whose outside fork byVedantMadaneon 2026-08-23 is recorded as a lead, not usage), with thecurrent GitHub/npm signals, the 2026-08-25 maintainer merge batch, the open
feature pull requests (Bind Action evaluation to the workflow PR head SHA #59, An Action that is hard to roll back is not ready for a beta #33, Should a policy change govern the pull request that changes it? #30, docs: record beta release candidate 41f8abf #17, build(deps-dev): bump @vitest/coverage-v8 from 3.2.7 to 4.1.11 #14, docs: record v0.1.0-beta.1 release, shadow no-go, and refreshed application evidence #19, fix: exclude compiled dist tests from vitest runs #16), and the
Dependabot backlog. Supersedes the 2026-08-24 register, which stays on file.
AGENTS.mdoperating snapshot revalidated to 2026-08-28: records the2026-08-25 merges of docs: record public activity evidence #46/test: cover runner-native dashed action inputs #47/docs: add CHANGELOG from tagged releases #51/test: add CODEOWNERS conformance fixtures #53/test: guard consumer documentation freshness #54/Describe PatchGate by the work it does #55 bringing
maintoc9d11cb, the completed CI 32806576723 and CodeQL 32806576725 runs onthat commit, the currently open branches (PR Bind Action evaluation to the workflow PR head SHA #59 green and waiting on the
required approving review, PR docs: add beta release and rollback guide #52, Dependabot build(deps): bump github/codeql-action/init from 4.37.7 to 4.37.8 #57/build(deps): bump github/codeql-action/analyze from 4.37.7 to 4.37.8 #58, PR build(deps-dev): bump typescript from 5.9.3 to 7.0.2 #12), and the
five-repository workspace list.
How I checked
2026-08-28 (stars, open issues, releases, PR check rollups, dist-tags,
download counts with their windows).
node scripts/check-doc-links.mjs: documentation link checks passed(80 Markdown files scanned).
their limits are unchanged, so no roadmap edit is required.
Evidence boundary
This is maintenance documentation only. It does not claim external adoption,
live integration, release readiness, or independent review; every merge it
records is labeled a maintainer decision.