chore: Apply final polish and gold standard improvements from audit

Author: lynnwallenstein

.devcontainer/boot-check.sh

@@ -9,9 +9,11 @@ else
     while IFS='=' read -r key value; do
         # Skip empty lines and comments
         if [[ -n "$key" && ! "$key" =~ ^# ]]; then
-            # Trim leading/trailing whitespace from key and value
-            key=$(echo "$key" | xargs)
-            value=$(echo "$value" | xargs)
+            # Trim leading/trailing whitespace
+            key="${key#"${key%%[![:space:]]*}"}"
+            key="${key%"${key##*[![:space:]]}"}"
+            value="${value#"${value%%[![:space:]]*}"}"
+            value="${value%"${value##*[![:space:]]}"}"
             export "$key=$value"
         fi
     done < ".env"

.devcontainer/devcontainer.json

@@ -21,7 +21,11 @@
         "GitHub.github-vscode-theme",
         "bierner.markdown-mermaid",
         "mechatroner.rainbow-csv",
-        "ms-vscode.makefile-tools"
+        "ms-vscode.makefile-tools",
+        "ms-azuretools.vscode-containers",
+        "ms-azuretools.vscode-docker",
+        "github.vscode-github-actions",
+        "github.vscode-pull-request-github"
       ],
       "settings": {
         "workbench.startupEditor": "none"

.env.example

@@ -10,5 +10,4 @@ SSH_PUBLIC_KEY=
 # Get your key at: https://aistudio.google.com/app/apikey
 GEMINI_API_KEY=
 
-
 # Add project specific secrets below

.github/workflows/devcontainer-test.yml

@@ -2,9 +2,9 @@ name: Devcontainer Build Validation
 
 on:
   push:
-    branches: [ main, booting ]
+    branches: [main, booting]
   pull_request:
-    branches: [ main ]
+    branches: [main]
 
 jobs:
   build-root:

AGENTS.md

@@ -41,7 +41,7 @@ It is critical to distinguish between the two development environments in this r
 ### Modifying the Generator (`install.sh`)
 
 - Changes to `install.sh` should be extremely rare. It must remain lightweight.
-- Ensure that the tarball extraction logic (`tar -xz --strip-components=2 "*/templates/"`) remains robust. It relies on GitHub's tarball structure.
+- Ensure that the tarball extraction logic (utilizing `--wildcards` for the `/templates` directory) remains robust. It relies on GitHub's tarball structure.
 
 ## 📝 Contribution & Maintenance Rules
 

install.sh

@@ -25,7 +25,7 @@ fi
 mkdir -p docs/decisions
 
 # Make scripts executable
-chmod +x .devcontainer/boot-check.sh scripts/setup-env.sh scripts/setup-gemini.sh scripts/start-container.sh
+chmod +x .devcontainer/boot-check.sh scripts/setup-env.sh scripts/setup-gemini.sh scripts/start-container.sh scripts/troubleshooting.sh
 chmod +x .githooks/*
 
 echo "✅ Bootstrap complete. Open in VS Code or Antigravity to start the Devcontainer."

scripts/setup-env.sh

@@ -72,8 +72,6 @@ if [ -n "$GEMINI_API_KEY" ]; then
     update_env "GEMINI_API_KEY" "$GEMINI_API_KEY"
 fi
 
-
-
 # Update the LICENSE file if it exists
 if [ -f "LICENSE" ] && [ -n "$GIT_NAME" ]; then
     CURRENT_YEAR=$(date +"%Y")

templates/.env.example

@@ -10,5 +10,4 @@ SSH_PUBLIC_KEY=
 # Get your key at: https://aistudio.google.com/app/apikey
 GEMINI_API_KEY=
 
-
 # Add project specific secrets below

templates/.github/CODEOWNERS

@@ -1,4 +1,5 @@
-# Default owners for everything
+# Default owners for everything. Note: team slugs like @core-maintainers 
+# are placeholders and must be updated to match teams in your GitHub organization.
 *       @core-maintainers
 
 # Architecture decisions require Tech Lead review

templates/AGENTS.md

@@ -55,7 +55,7 @@ When adding or modifying automation scripts for the devcontainer, you must adher
 
 ## 🤖 Token Optimization & CLI Usage
 
-- **GitHub CLI:** The `gh` command is available in this container. If a `GITHUB_TOKEN` is provided in `.env`, the host's CLI will be authenticated and `gh auth setup-git` will automatically configure it as your Git credential helper. This enables seamless HTTPS Git operations in the environment. See [.env.example](.env.example) for required `GITHUB_TOKEN` scopes.
+- **GitHub CLI:** The `gh` command is available in this container. Use `gh auth login` to authenticate. This enables seamless GitHub operations and can configure Git as your credential helper.
 - **Offload Structured Edge-Tasks:** To preserve your context window (tokens) for complex logic, use the Gemini CLI (`@google/gemini-cli`) installed in this container for well-structured tasks.
 - **Usage:** Run `gemini` in the terminal to start an interactive session, or `gemini -p "<prompt>"` for one-shot tasks.
 - **Examples:** Ask the CLI to review code, analyze architecture, or investigate issues—this keeps your IDE context window focused on the primary task.