[Selcukatli]

Summary

• scaffold-case.sh --add <case-dir> <o1a|eb1a|both> adds a petition workspace to an existing case, e.g. an O-1A case that is now also pursuing an EB-1A.
• It creates only the new petition directory. It leaves resources/, case-overview.md and any existing petition directory untouched.
• It refuses if the folder isn't a case (no case-overview.md), if the petition directory already exists, or if the type is missing or unknown.
• A plain scaffold into a non-empty folder still refuses, and its error message now points to --add.
• Updated the petition-workspace skill, the /new-case command and the README.

Tests

• New scripts/test-scaffold.sh (15 checks) runs in npm test and as a CI step.
• Against the old script it fails with exit 2, so it catches the missing feature.

Verification

• Ran it by hand: scaffolded an O-1A case in a temp folder, then ran --add <case> eb1a, which created eb1a/ with its 10 criteria. Running --add again refused.
• The test confirms by checksum that --add changes none of the existing case files.
• In the added workspace, add-evidence.mjs filed a document and build-portal.mjs built the review packet over both workspaces.
• Not yet verified: the new CI step on GitHub Actions, and an agent picking --add from the /new-case command text.

Note

The original request was only the title "another workspace". This PR reads it as adding another petition-type workspace to an existing case.

🤖 Generated with Claude Code