security: remove hardcoded VPS SSH credentials from committed files

[Copilot]

SSH password was hardcoded in plain text across four committed files (.github/copilot-instructions.md, SKILLS.md, deploy.sh). This replaces it with an environment-variable-based pattern and gitignores the intended local credentials file.

Changes

• .gitignore — adds .copilot-credentials.md to prevent the local credentials file from ever being committed
• .github/copilot-instructions.md — replaces hardcoded SSH command with a reference to .copilot-credentials.md in both the Infrastructure section and Critical Rules #10
• deploy.sh — loads VPS_SSH_PASS from .env or the shell environment; uses SSHPASS env var + sshpass -e to avoid password exposure in process listings (ps aux); fails fast with a clear error if unset
• SKILLS.md — updates SSH deployment examples to match the new pattern
• .env.example — documents the VPS_SSH_PASS variable

# Before — password visible in process list
sshpass -p '#Crowlr@2023' ssh $SSH_OPTS "$SERVER" "..."

# After — password passed via env var, never in argv
export SSHPASS="$VPS_SSH_PASS"
sshpass -e ssh $SSH_OPTS "$SERVER" "..."

⚠️ The password existed in git history prior to this PR. Rotating the VPS SSH password is recommended to fully close the exposure.

Original prompt

continue

[Chronological Review: The conversation began with the user requesting a check on recent changes made to their projects, specifically regarding the creation of a credentials file and updates to documentation. The user then inquired about the usefulness of the Context Engine and MCP server, followed by questions about the options available when selecting CLOUD. The user expressed a desire to commit changes and delegate tasks to a cloud agent, and finally asked if the agent was actively working.]

[Intent Mapping:

1. "check what was done and apply to your projects!" - User wants to verify recent changes and ensure they are applied.
2. "does the Context engine or the MCP server is getting useful?" - User seeks feedback on the utility of their systems.
3. "when I set CLOUD I only see Agent, Ask or plan, no more llm choice like 4.6!" - User is confused about the options available in the CLOUD setting.
4. "Commit Changes and Delegate: 'Delegate to cloud agent'" - User wants to commit changes and delegate tasks.
5. "are you working?" - User is checking on the agent's activity status.]

[Technical Inventory:

• Tools/Commands: git commands for checking the status and ignoring files, cloud agent functionalities.
• Files: .copilot-credentials.md, copilot-instructions.md, CLAUDE.md, README.md.
• Concepts: Git version control, cloud agent delegation, context engine functionality.]

[Code Archaeology:

• .copilot-credentials.md: Created to store sensitive information securely.
• copilot-instructions.md: Updated to reference the new credentials file.
• CLAUDE.md: Updated to include references to the credentials file.
• README.md: Current file being edited by the user.]

[Progress Assessment:

• Completed: Creation of .copilot-credentials.md and updates to copilot-instructions.md and CLAUDE.md.
• Pending: User's inquiry about the cloud agent's functionality and the delegation of tasks.]

[Context Validation: All critical information regarding recent changes, user inquiries, and the current state of the project is captured.]

[Recent Commands Analysis:

• Last Agent Commands: "Commit Changes and Delegate: 'Delegate to cloud agent'" - User requested to commit changes and delegate tasks.
• Tool Results Summary: No specific results were returned from the last command as it was a user request.
• Pre-Summary State: The agent was actively engaged in processing the user's request to commit changes and delegate tasks when the token budget was exceeded.
• Operation Context: The user is focused on ensuring that recent changes are committed and tasks are delegated to a cloud agent for further processing.]

1. Conversation Overview: - Primary Objectives: - "check what was done and apply to your projects!" - Verify recent changes. - "does the Context engine or the MCP server is getting useful?" - Assess the utility of systems. - "when I set CLOUD I only see Agent, Ask or plan, no more llm choice like 4.6!" - Clarify options in CLOUD settings. - "Commit Changes and Delegate: 'Delegate to cloud agent'" - Commit changes and delegate tasks. - "are you working?" - Check on agent's activity. - Session Context: The conversation flowed from checking recent project updates to inquiries about system functionality and committing changes. - User Intent Evolution: The user transitioned from verifying changes to seeking clarity on system options and delegating tasks.

2. Technical Foundation:

• Git: Version control system used for managing project files.
• Cloud Agent: Functionality for delegating tasks to a cloud-based system.
• Context Engine: A system the user is evaluating for its usefulness.

3. Codebase Status:

• .copilot-credentials.md:
  • Purpose: Store sensitive information securely.
  • Current State: Newly created.
  • Key Code Segments: Contains SSH passwords, MySQL root password, and deployment commands.
  • Dependencies: Related to copilot-instructions.md for referencing credentials.
• copilot-instructions.md:
  • Purpose: Document architecture and rules.
  • Current State: Updated to reference .copilot-credentials.md.
  • Key Code Segments: Lines updated to indicate where credentials are stored.
• CLAUDE.md:
  • Purpose: Quick reference to credentials.
  • Current State: Updated to include references to .copilot-credentials.md.

4. Problem Resolution:

• Issues Encountered: User confusion regarding the options available in the CLOUD setting.
• Solutions Implemented: Updates made to documentation to clarify usage.
• Debugging Context: Ongoing inquiries about system functionality.
• Lessons Learned: Importance of clear documentation for user guidance.

5. Progress Tracking:

• Completed Tasks: Creation of .copilot-credentials.md and updates to related documentation.
• Partially Complete Work: User's inquiry about cloud agent functionality and task delegation.
• Validated Outcomes: Changes confirmed as committed and documented.

6. Active Work State:

• Current Focus: User was wo...

Created from VS Code.

---

💡 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.