Chore: Cleanup root directory

.gitignore

@@ -87,7 +87,7 @@ dsa_pub.pem     # Public key (safe to commit if needed)
 codesign*
 *.bak
 *.backup
-
+*.provisionprofile
 
 # Release artifacts (keep in build/ folder)
 # Uncomment these if you want to commit release artifacts:

CONTRIBUTING.md

@@ -29,7 +29,7 @@ Please be respectful to maintainers and disclose AI assistance.
 
 2. Run the setup script to install tools, configure git hooks, and generate the Xcode project:
    ```bash
-   ./setup.sh
+   ./scripts/setup.sh
    ```
 
 3. Open in Xcode and build:
@@ -42,7 +42,7 @@ Please be respectful to maintainers and disclose AI assistance.
 
 ### Formatting & Linting
 
-Code formatting and linting are automatically enforced via git hooks (installed by `./setup.sh`):
+Code formatting and linting are automatically enforced via git hooks (installed by `./scripts/setup.sh`):
 
 - **SwiftFormat**: Handles code formatting
 - **SwiftLint**: Enforces coding standards
@@ -176,7 +176,7 @@ Ora uses [Sparkle](https://sparkle-project.org/) for automatic updates. All buil
    ```bash
    brew install --cask sparkle
    ./setup-sparkle-tools.sh
-   ./setup-sparkle.sh
+   ./scripts/setup-sparkle.sh
    ```
    This generates DSA keys in `build/` directory.
 
@@ -187,7 +187,7 @@ Ora uses [Sparkle](https://sparkle-project.org/) for automatic updates. All buil
 
 4. **Create a release:**
    ```bash
-   ./create-release.sh 0.0.2 build/dsa_priv.pem
+   ./scripts/create-release.sh 0.0.2 build/dsa_priv.pem
    ```
    This builds, signs, and prepares release files in `build/`.
 

README.md

@@ -70,7 +70,7 @@ See the [Wiki](https://github.com/the-ora/browser/wiki) for comprehensive docume
    ```bash
    git clone https://github.com/the-ora/browser.git
    cd browser
-   ./setup.sh
+    ./scripts/setup.sh
    ```
 
 2. Open and build:

SECURITY.md

@@ -19,7 +19,7 @@ Ora Browser uses Ed25519 cryptographic keys to sign and verify app updates for s
 ### Setup Process
 1. **First machine**: Keys auto-generated and saved appropriately
 2. **Additional machines**: Copy `.env` file from first machine
-3. **Release process**: `./create-release.sh` handles key management automatically
+3. **Release process**: `./scripts/create-release.sh` handles key management automatically
 
 ### Security Notes
 - `.env` is in `.gitignore` - it will never be committed
@@ -29,7 +29,7 @@ Ora Browser uses Ed25519 cryptographic keys to sign and verify app updates for s
 
 ## 🔍 Security Checks
 
-Run `./check-security.sh` to verify:
+Run `./scripts/check-security.sh` to verify:
 - Private key exists but is not tracked by git
 - Public key is available for app integration
 - `.gitignore` properly excludes sensitive files