@lousy-agents/cli 5.17.16 → 5.18.1

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@lousy-agents/cli",
-    "version": "5.17.16",
+    "version": "5.18.1",
     "description": "CLI scaffolding tool that sets up projects with structure, instructions, and feedback loops for AI coding assistants",
     "type": "module",
     "repository": {

package/ui/copilot-with-react/.agents/skills/feature-to-plan/SKILL.md

@@ -55,7 +55,7 @@ Work in a read-only planning phase first. If the runtime provides a dedicated pl
 
 1. **Discover product and engineering context.** Read whatever conventional files the repo provides — for example `AGENTS.md`, `README.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, `CONTRIBUTING.md`, anything under `.github/instructions/`, or product docs under `docs/`. Don't assume any specific file exists; use what's there.
 2. **Seed Context & Goal.** Based on the argument:
-   - **Issue reference (`#N` or matches `^\d+$`):** fetch the issue and treat its Context & Goal and Acceptance Criteria sections (if present) as the starting point. Note any cross-reference IDs (e.g., a beads ID) in the issue footer.
+   - **Issue reference (`#N` or matches `^\d+$`):** fetch the issue and treat its Context & Goal and Acceptance Criteria sections (if present) as the starting point. Note any cross-reference IDs in the issue footer.
 
      ```bash
      gh issue view <N> --json title,body,labels,comments

package/ui/copilot-with-react/package.json

@@ -23,7 +23,7 @@
     "devDependencies": {
         "@biomejs/biome": "2.5.3",
         "@eslint/eslintrc": "3.3.6",
-        "@lousy-agents/mcp": "5.17.15",
+        "@lousy-agents/mcp": "5.18.0",
         "@modelcontextprotocol/server-sequential-thinking": "2026.7.4",
         "@testing-library/jest-dom": "7.0.0",
         "@testing-library/react": "16.3.2",