docs: bring README current after Release Day - #209
Draft
WalksWithASwagger wants to merge 1 commit into
Draft
WalksWithASwagger wants to merge 1 commit into
WalksWithASwagger wants to merge 1 commit into
Conversation
Refresh the root README so it matches the live portal, the May 29 deadline that already passed, and the commands that actually exist. Leave recording-rights copy untouched. Mark still-unknown follow-ups as TODO for KK. Co-authored-by: Kris Krüg <WalksWithASwagger@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 tasks
This branch was successfully deployed
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
2 participants
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.
The README still talked like we were in Release Month. We are not. May 29 already happened.
This pass updates the root README so it matches the live portal, the commands that actually exist, and GitHub as the only tracker. Recording rights / clip usage stay exactly as they were — confirm with Mark. I did not add or change Adobe claims.
Still unknown, so I left them as TODO for KK: whether the public form stays open, whether any work landed, social cadence after May 29, the long article, and the optional zine.
Secrets note: Varlock, not 1Password. Variable names only. This repo still has no
.env.schema— also a TODO for KK if you want one in-tree.Closes #208
Verification
npm run docs:links— passed (33 maintained files)npm run docs:links:all— passed (158 files)npm run seo:index-hygiene— passednpm run test:index-hygiene— 7 passednpm run eval— passed locally and in CInpm run test:agentic— 30 passednpm run check:python— passednpm run check/ CI Eval — every real gate passed, thennpm audit --audit-level=moderatefailed on a pre-existingsharphigh advisory (<0.35.4, GHSA-rgj7-g3m4-5g8c). Last successful Eval onmainwas 2026-09-06. Docs-only PR; I did not bump dependencies.Agentic Delivery
Closes #208only when every acceptance criterion is met