update readme for new deploy script and bump version to 1.0

Readme changes:
- Document that deployment directory must exist first
- Show mkdir -p commands before deploy
- Explain atomic deployment behavior (extracts to /tmp first)

Version bump to 1.0:
- Major refactoring: renamed app to jrunner
- Simplified deployment script
- Updated documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

jrunner/src/main/java/jrunner/jrunner.java

@@ -39,7 +39,7 @@ public class jrunner {
         Timestamp tsStart = null;
         Timestamp tsEnd   = null;
 
-        msg = "jrunner version 0.41";
+        msg = "jrunner version 1.0";
         msg = msg + nl + "-scu       source jdbc url";
         msg = msg + nl + "-scn       source username";
         msg = msg + nl + "-scp       source passowrd";

readme.md

@@ -39,15 +39,23 @@ cd jrunner
 ## deploy
 
 ### using the deploy script (recommended)
+
+First, create the deployment directory:
+```
+sudo mkdir -p /opt/jrunner
+```
+
+Then deploy:
 ```
 # Deploy to /opt/jrunner (default, creates system-wide symlink)
 ./deploy.sh
 
 # Deploy to custom location (for testing, no symlink)
+sudo mkdir -p /opt/jrunner-test
 ./deploy.sh /opt/jrunner-test
 ```
 
-The script builds and deploys in one step. When deploying to the default location (`/opt/jrunner`), it creates a symlink at `/usr/local/bin/jrunner` so you can run `jrunner` from anywhere.
+The script builds, extracts to a temporary location, and only updates the target directory after the build succeeds. This ensures your existing deployment stays intact if the build fails. When deploying to `/opt/jrunner`, it creates a symlink at `/usr/local/bin/jrunner`.
 
 ### manual deployment
 ```