Skip to content

fix(claude-apps-gateway): PR #282 doc follow-ups; fix stale Desktop-default comment - #283

Open
bsnehanshu wants to merge 1 commit into
mainfrom
fix/pr-282-followups-and-bootstrap-desktop-defaults
Open

bsnehanshu wants to merge 1 commit into
mainfrom
fix/pr-282-followups-and-bootstrap-desktop-defaults

Conversation

@bsnehanshu

Copy link
Copy Markdown
Collaborator

What

Three defects left over from #282, all in text/examples the diff's own hunks didn't cover, plus one related bug found independently in claude-apps-gateway-bootstrap.

In claude-apps-gateway/:

  1. README.md:246 — the link to docs/gotchas.md#20-three-ways-the-desktop-block-itself-bites was missing GitHub's actual slug suffix. The target heading is ## 20. Three ways the desktop block itself bites **[hit live]**, and the double space before the bold marker produces a double-hyphen slug (--hit-live), matching the repo's existing precedent at docs/gotchas.md#13-config-is-baked--the-image-is-per-environment. The link landed at the top of the file instead of the gotcha it pointed to.
  2. docs/deployment.md:43-44 — an orphaned "plus" left over from rewording the jp. clause: "...au., plus\nand jp. for some models...".
  3. cdk/README.md and README.md still shipped claude-opus-4-8 in two example blocks (cdk/README.md's local-dev example, README.md's failover example), directly contradicting the "shipped catalog is Claude Opus 5..." line chore(claude-apps-gateway): bump pinned Claude Code to 2.1.229; Opus 5 as the catalog default #282 added earlier in the same files.

In claude-apps-gateway-bootstrap/ (pre-existing, unrelated to #282):

The comment above the chatTabEnabled passthrough in server.js claimed omitting any of the three Desktop surface toggles "keeps the client default." True for coworkTabEnabled/isClaudeCodeForDesktopEnabled (show unless false), false for chatTabEnabled (hidden unless explicitly true, per the gateway README's Desktop overlay table). The example config set only 1 of the 3 toggles as a result — now sets all three explicitly, and the comment states the asymmetry.

Why

All four are mechanical — no design judgment involved, just checking that changed lines are consistent with the rest of the file/repo they live in, not just internally correct. Caught in an independent second-pass review after #282 merged.

Verification

🤖 Generated with Claude Code

…efault comment

Three defects left over from #282 (chore(claude-apps-gateway): bump pinned
Claude Code to 2.1.229; Opus 5 as the catalog default), all in text/examples
the diff's own hunks didn't cover:

- README.md:246 linked docs/gotchas.md#20-three-ways-the-desktop-block-itself-bites,
  but the target heading's `**[hit live]**` suffix makes GitHub's actual slug
  end in `--hit-live` (double hyphen, matching the repo's existing
  #13-config-is-baked--the-image-is-per-environment precedent). The link
  landed at the top of the file instead of the gotcha it was meant to point at.
- docs/deployment.md:43-44 read "...au., plus\nand jp. for some models..." —
  an orphaned "plus" left over when the jp. clause was reworded.
- cdk/README.md's local-dev example and README.md's failover example still
  shipped claude-opus-4-8, directly contradicting the "shipped catalog is
  Claude Opus 5..." line #282 added earlier in the same file.

Also fixes a related but separate bug in claude-apps-gateway-bootstrap: the
comment above the chatTabEnabled passthrough claimed omitting a toggle "keeps
the client default" for all three surface toggles. That's true for
coworkTabEnabled/isClaudeCodeForDesktopEnabled (show unless false) but wrong
for chatTabEnabled, which is hidden unless explicitly set true per the
gateway README's Desktop overlay table. The example config only set 1 of 3
toggles as a result; now sets all three explicitly.

Verified: shellcheck clean, setup-helpers.test.sh 19/19, stamp-config.test.sh
9/9, node --check on server.js, bootstrap authorize.test.mjs 5/5, no
remaining 2.1.218/claude-opus-4-8 references in claude-apps-gateway/.
@aws-samples aws-samples deleted a comment from mergify Bot Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant