GeezerVison

Clean-ups from the v1.0.888 release and the first ChatGPT and Anthropic directory submissions. Works through the actionable items in #900; the items that wait on external replies (demo recording URL, Verified organization, Ubuntu 26.04 re-validation) stay open there.

Docs

• docs/stackql_release_process.md: step 10 corrected (the pin PR runs stdio-plugins, the mcp-packaging validation, Lint and CodeQL; packaging/** is in the Build workflow's paths-ignore, so the matrix does not run); step 7a notes that stackql is a trusted Chocolatey package with automated moderation; step 11 records where the OpenAI organization ID lives, who completes business verification, and uploading the first ZIP early to read the validator (mcp_configuration_excluded means the allowlist has not landed); step 12 records the holds that are by design, the answers given at submission, auto-publish and the push webhook.
• packaging/mcpb/docs/anthropic-submission.md: new section on what the validator reports and what to leave alone (the node launcher hold, the five listing-field warnings, the Verified organization note, the undocumented classification block); the one-time checklist now records the 2026-11-05 submission (surfaces, data handling answers, compliance contact, webhook) and keeps the reviewer decision and Verified organization open.

Links

https://stackql.io/docs redirects to the homepage, so the documentation link in both plugin manifests (and the derived Codex overlay), both plugin READMEs, the shared setup skill and its two vendored copies, the MCPB manifest templates and fixtures, the npm and PyPI READMEs, pyproject.toml and the registry server.template.json now points at https://stackql.io/getting-started; the two "provider pages" sentences point at https://stackql.io/providers. Both plugins were re-rendered at 1.0.888 afterwards and match the committed files.

Tooling

• packaging/mcpb/scripts/render-platforms.sh: stamps package-lock.json (top-level and packages[""]) with the version too; the lockfile had stayed at 0.12.778 through two releases. Committed here at 1.0.888.
• packaging/mcpb/scripts/smoke-test.py: a second reader thread keeps the launcher's last 40 stderr lines; fail() prints them, and the exit path waits up to a second for them. The dotnet Windows ARM64 flake in the 1.0.888 mcp-packaging run left nothing to diagnose.
• .github/workflows/build.yml: cicd/python/attach_build_artifacts.py and its test added to both paths-ignore lists (a release-tooling fix ran the full matrix in attach-artifacts-utf8 #897); dockermerge gets max-parallel: 1 after both merge variants hit Docker Hub 429 Too Many Requests twice on 2026-11-05.

Test plan

• python packaging/openai-plugin/scripts/validate.py and python packaging/mcpb/scripts/validate-claude-plugin.py: pass.
• make npm-manifest VERSION=1.0.888 after the edits: re-rendered files identical to the committed ones apart from the newly stamped lockfile.
• python -m py_compile packaging/mcpb/scripts/smoke-test.py, bash -n packaging/mcpb/scripts/render-platforms.sh, js-yaml .github/workflows/build.yml: pass. cicd/python unit tests: 9 passed.
• CI: stdio-plugins (render check, claude plugin validate --strict, smoke tests on four platforms), mcp-packaging validation (exercises the smoke test change), and the full Build because the workflow file changed.

🤖 Generated with Claude Code