Fix documentation inconsistency: standardize zip download error language

[Copilot]

Problem

The documentation in .github/copilot-instructions.md used inconsistent language to describe the same Coinbase and Phantom wallet preparation issue:

• Line 46: "zip download issues" (vague)
• Lines 47-48: "zip download fails" (generic failure)
• Line 59: "zip download returns invalid files (9 bytes)" (specific details)

This inconsistency made the documentation confusing and less helpful for developers troubleshooting the issue.

Solution

Standardized all references to use the more specific and descriptive language: "zip download returns invalid 9-byte files"

Changes Made

Updated 4 lines in .github/copilot-instructions.md:

• Changed generic "zip download issues" to specific error description
• Replaced "zip download fails" with detailed "zip download returns invalid 9-byte files"
• Normalized format for consistency across all references

Impact

• Clearer documentation: Developers now get specific details about what exactly fails
• Better troubleshooting: The "9-byte files" detail helps identify the root cause
• Consistent messaging: All references to this issue now use identical language
• Maintained context: No functional changes, purely documentation clarity improvement

The documentation now clearly communicates that the issue isn't just a generic failure, but specifically that the zip downloads return invalid 9-byte files, which is more actionable information for developers.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>The documentation inconsistently refers to 'zip download fails' and 'zip download returns invalid files (9 bytes)'. Consider using consistent language to describe the same issue - either 'zip download fails' or 'returns invalid 9-byte files' throughout the document.</issue_title>
<issue_description>The documentation inconsistently refers to 'zip download fails' and 'zip download returns invalid files (9 bytes)'. Consider using consistent language to describe the same issue - either 'zip download fails' or 'returns invalid 9-byte files' throughout the document.

npm run prepare-coinbase    # ⚠️ Known issue: zip download returns invalid files (9 bytes)
npm run prepare-phantom     # ⚠️ Known issue: zip download returns invalid files (9 bytes)

Originally posted by @copilot-pull-request-reviewer in #71 (comment)</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #73

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[joe10832]

@copilot

[Copilot]

Pull Request Overview

This PR standardizes documentation language to improve clarity and consistency when describing the Coinbase and Phantom wallet preparation issues.

• Replaces vague "zip download issues" and generic "zip download fails" with specific "zip download returns invalid 9-byte files"
• Ensures consistent error messaging across all references to the same underlying issue
• Provides more actionable troubleshooting information by specifying the exact failure behavior

[joe10832]

<issue_title>copilot-setup-steps</issue_title>
<issue_description>/.github/copilot-instructions.md
/.github/instructions/**/*.instructions.md
**/AGENTS.md
/CLAUDE.md
/GEMINI.md</issue_description> name: "Copilot Setup Steps"

Automatically run the setup steps when they are changed to allow for easy validation, and

allow manual testing through the repository's "Actions" tab

on:
workflow_dispatch:
push:
paths:
- .github/workflows/copilot-setup-steps.yml
pull_request:
paths:
- .github/workflows/copilot-setup-steps.yml

jobs:

The job MUST be called copilot-setup-steps or it will not be picked up by Copilot.

copilot-setup-steps:
runs-on: ubuntu-latest

# Set the permissions to the lowest permissions possible needed for your steps.
# Copilot will be given its own token for its operations.
permissions:
  # If you want to clone the repository as part of your setup steps, for example to install dependencies, you'll need the `contents: read` permission. If you don't clone the repository in your setup steps, Copilot will do this for you automatically after the steps complete.
  contents: read

# You can define any steps you want, and they will run before the agent starts.
# If you do not check out your code, Copilot will do this for you.
steps:
  - name: Checkout code
    uses: actions/checkout@v5

  - name: Set up Node.js
    uses: actions/setup-node@v4
    with:
      node-version: "20"
      cache: "npm"

  - name: Install JavaScript dependencies
    run: npm ci

@copilot