docs: surgically prune plan-blocks references to fix remaining doc drift#142
Merged
Conversation
dembrane-sam-bot
enabled auto-merge
July 14, 2026 05:13
spashii
added a commit
that referenced
this pull request
Jul 14, 2026
…oot CVE (#143) ## What broke Every PR branch went CI-red yesterday (#138–#142 all fail the trivy step; the older green PRs just ran their checks before the CVEs published). Two causes: 1. **curl CVE-2026-5773 / CVE-2026-6276** — Debian shipped the fix (`deb13u4`) but the image stays on `deb13u3`: `apt-get upgrade -y` only runs at layer-build time, and `cache-from: type=gha` keeps serving the cached apt layer. The dockerfile's own comment history (gh CVE-2026-48501) shows this trap has bitten before. 2. **CVE-2026-39822** — Go stdlib `os.Root` symlink following inside `/usr/bin/gh` (built with Go 1.26.4, fixed in 1.26.5). Same family as the eight gh Go-stdlib CVEs already in `.trivyignore`; Sam runs gh against repos it cloned itself, not attacker-controlled trees. ## The fix - New `USER root → apt-get update && upgrade → USER sam` layer **below the source COPY**, so it busts on every commit build and picks up security patches, while the expensive layers above stay cached. Known edge documented in the comment: re-running CI on a bit-identical branch still hits the cache; merging main forces the refresh. - `CVE-2026-39822` added to the gh block in `.trivyignore` with rationale. ## Merge order **Merge this first**, then update the red branches from main (#138, #139, #140, #141, #142) — same unblock shape as June's #130. Found during the 2026-07-14 follow-up to the monthly maintenance pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: sam-dembrane <sam-dembrane@sam2ks-MacBook-Pro.local> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
What is this change?
Surgically prunes the residual references to "plan blocks" in and . These lines previously claimed "plan blocks" were a live feature or a valid judgment-call option when they are not implemented or supported by Slack's public Block Kit API. Also fixes a typo path reference to by updating it to .
What did Sam notice that led to this?
During today's daily-maintenance run, a Claude Opus mentor review flagged that while the main description of plan blocks was correctly marked "not yet implemented," two high-level list/frontmatter index-level references to "plan blocks" still remained in the workspace capability and skill description files.
Tier?
Tier 1 (Prose/Documentation).
Confidence?
High. This perfectly completes the cleanup of doc-vs-reality drift on Slack's visual and status capabilities.