Skip to content

docs: correct deck deploy install path - #8

Open
m4ttheweric wants to merge 1 commit into
mainfrom
chore/deploy-path-doc
Open

docs: correct deck deploy install path#8
m4ttheweric wants to merge 1 commit into
mainfrom
chore/deploy-path-doc

Conversation

@m4ttheweric

@m4tthewericm4ttheweric commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Follow-up housekeeping to #7.

The manifest-first plan and spec described deck's deploy installing over ~/.local/bin/deck, but deck's launchd plist runs the binary from ~/.mattstack/deck/bin/deck (install.sh's BIN_DIR). The shipped scripts/deploy.ts was already corrected during review to install there (atomic temp + mv); this brings the two docs in line so the stale path can't be copied out of them later.

Docs-only, no code change.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated deployment guidance to install the deck executable at the location used by its launch configuration.
    • Deployment instructions now include creating the destination directory and safely replacing the executable.
    • Updated self-deployment examples to reflect the standardized installation path.

The plan + spec showed ~/.local/bin/deck, but the launchd plist runs the
binary from ~/.mattstack/deck/bin/deck (install.sh's BIN_DIR). Shipped
scripts/deploy.ts already installs there with an atomic temp+rename; this
aligns the docs so nobody copies the stale path.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitaiBot commented Aug 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e8ce55a6-875f-4a2d-8fd0-34c0e46656c4

📥 Commits

Reviewing files that changed from the base of the PR and between 195d9a2 and c22694b.

📒 Files selected for processing (2)
  • docs/superpowers/plans/2026-08-28-deck-manifest-first.md
  • docs/superpowers/specs/2026-08-28-deck-manifest-first-design.md

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.


📝 Walkthrough

Walkthrough

The deployment plan and design specification now install deck at ~/.mattstack/deck/bin/deck. The plan also documents directory creation and atomic replacement through a same-directory temporary file and rename.

Changes

Deck deployment

Layer / File(s)Summary
Deployment path and installation procedure
docs/superpowers/plans/2026-08-28-deck-manifest-first.md, docs/superpowers/specs/2026-08-28-deck-manifest-first-design.md
The deployment destination now matches the launchd-registered path. The plan creates the target directory, installs an executable temporary sibling, and atomically renames it into place. The specification retains the restart and board re-polling steps.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk:⚪ Minimal · up to c2269

This documentation-only change aligns the documented deploy path with the intended installation location; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Description Check✅ PassedCheck skipped - CodeRabbit’s high-level summary is enabled.
Title check✅ PassedThe title clearly and concisely describes the documentation change to the deck deployment install path.
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/deploy-path-doc

Comment @coderabbitai help to get the list of available commands.

Sign up for freeto 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

@m4ttheweric