Skip to content

docs: add pilotctl quickstart to CLI reference and getting-started guide (PILOT-225)#17

Open
hank-pilot wants to merge 1 commit into
mainfrom
hank/PILOT-225-quickstart-docs
Open

docs: add pilotctl quickstart to CLI reference and getting-started guide (PILOT-225)#17
hank-pilot wants to merge 1 commit into
mainfrom
hank/PILOT-225-quickstart-docs

Conversation

@hank-pilot
Copy link
Copy Markdown
Contributor

What

Documents the new pilotctl quickstart subcommand (added in TeoSlayer/pilotprotocol#210).

Changes

  • CLI Reference (src/pages/docs/cli-reference.astro): New "Quickstart" section with full 3-step walkthrough, command syntax, --json flag, return values, and the canonical 3-command pattern with examples.
  • Getting Started (src/pages/docs/getting-started.astro): TOC entry + callout linking to the CLI reference quickstart section.

Why

PILOT-36 stranger tests showed users had to read SKILL.md files to find the 3-command getting-started pattern. pilotctl quickstart solves this; the docs make it discoverable from the website.

Fixes: PILOT-225

…ide (PILOT-225)

Adds documentation for the new `pilotctl quickstart` subcommand:
- CLI reference: full section with 3-step walkthrough, command syntax, flags, return values
- Getting started: TOC entry + callout linking to CLI reference

PILOT-225 companion docs.
@github-actions
Copy link
Copy Markdown

🚀 Preview deployed to Cloudflare Pages

  • Commit deploy URL: https://30edb005.pilotprotocol.pages.dev
  • Branch alias: https://hank/PILOT-225-quickstart-docs.pilotprotocol.pages.dev (may take ~30s to propagate)
  • Commit: fbb021a35cf8c1da16f4dcd3ea0c09a7fef18331

@hank-pilot
Copy link
Copy Markdown
Contributor Author

🛑 Sibling closed without mergingTeoSlayer/pilotprotocol#210

This PR depends on changes in that sibling. With it closed-no-merge, this PR can't land in its current shape.

Options:

  1. Open a replacement sibling PR and link it here
  2. Close this PR (Hank will mark the ticket Won't Fix)
  3. Manually rework this PR to not depend on the sibling

@matthew-pilot — operator review needed.

Posted by Hank (auto)

@hank-pilot
Copy link
Copy Markdown
Contributor Author

🔍 Drift detected — the PR body still references the closed sibling TeoSlayer/pilotprotocol#210, but a replacement is open at TeoSlayer/pilotprotocol#177 (same ticket PILOT-225, by @matthew-pilot).

Replacement #177 status: open, arch-gates CI failing (7/8 checks green).

Action needed: update the PR body to reference TeoSlayer/pilotprotocol#177 instead of #210 so the dependency chain is correct.

Posted by Hank (auto)

@hank-pilot
Copy link
Copy Markdown
Contributor Author

📈 Replacement sibling updateTeoSlayer/pilotprotocol#177 is now mergeable (CI gates all passing).

The original sibling #210 was closed without merging, but the replacement (same ticket PILOT-225) has cleared all checks. The PR body still references #210 — once updated to #177, the dependency chain should be healthy.

Reminder: update the PR body from TeoSlayer/pilotprotocol#210TeoSlayer/pilotprotocol#177.

Posted by Hank (auto)

@hank-pilot
Copy link
Copy Markdown
Contributor Author

⚠️ Correction — please disregard the previous comment. The replacement sibling TeoSlayer/pilotprotocol#177 is still unstable (Architecture gates failing: 7/9 checks green). No state change has occurred — the PR body drift still needs resolution.

Posted by Hank (auto)

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