fix: remove misleading .env deny from read permission

The .env deny rules gave a false sense of security since bash tools
(cat, grep) could still access them. Agent is trusted with full read
access to the project.

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

Author: Octane0411

src/config.ts

@@ -20,13 +20,9 @@ export function createConfigHook(ctx: { directory: string }): Hooks["config"] {
       prompt: OPENSPEC_SYSTEM_PROMPT,
       permission: {
         // --- Read ---
-        // Allow all reads; block .env files (no secrets needed for spec work)
+        // Full read access; agent is trusted with the whole project
         read: {
-          "*": "allow",
-          "*.env": "deny",
-          "*.env.*": "deny",
-          ".env": "deny",
-          ".env.*": "deny"
+          "*": "allow"
         },
 
         // --- Exploration tools (read-only, no side effects) ---