change: dangerous tools are now prohibited by default

Safer posture for a public package. Opt in with DangerousTools::allow();
prohibit()/the facade re-lock. Adds a reflection test for the shipped default;
docs (README, tools, SECURITY) updated. 100% coverage (784/784).

Author: kevariable

README.md

@@ -103,13 +103,13 @@ class WeatherTool implements Tool
 
 ### Dangerous tools
 
-`shell_exec`, `file_write`, and `delete_file` are shipped but every call is gated. Lock them down with one static call (e.g. in a production service provider):
+`shell_exec`, `file_write`, `file_append`, `delete_file`, `mkdir`, `move_file`, and `db_query` are shipped but **prohibited by default** — every call is gated like Laravel's `DB::prohibitDestructiveCommands()`. Opt in when you trust the environment:
 
 ```php
 use Kevariable\PhpclawLaravel\DangerousTools;
 
-DangerousTools::prohibit();   // any dangerous tool now throws DangerousToolsProhibitedException
-DangerousTools::allow();      // re-enable (the default)
+DangerousTools::allow();      // enable (off by default) — any dangerous tool works
+DangerousTools::prohibit();   // re-lock; calls throw DangerousToolsProhibitedException
 
 // or via the facade:
 Phpclaw::prohibitDangerousTools();

SECURITY.md

@@ -9,4 +9,4 @@ Please include enough detail to reproduce the issue. You will get an acknowledge
 
 ## Notes on the agent's powerful tools
 
-This package can register tools that read the filesystem and make HTTP requests. The destructive/system tools (shell execution, process control, raw database queries, file writes/deletes) are intentionally **not** shipped enabled — they are only available if you add them yourself. Treat any agent that can run tools as a privileged actor and scope the `phpclaw.tools_root`, the registered tools, and the browser token accordingly.
+This package can register tools that read the filesystem and make HTTP requests. The dangerous tools (shell execution, file writes/appends/deletes, directory creation, file moves, raw database queries) ship registered but are **prohibited by default** — every call is gated and throws unless you explicitly call `Kevariable\PhpclawLaravel\DangerousTools::allow()`. Enable them only in environments you trust. Treat any agent that can run tools as a privileged actor and scope the `phpclaw.tools_root`, the registered tools, and the API/browser tokens accordingly.

docs/tools.md

@@ -57,7 +57,7 @@ use Kevariable\PhpclawLaravel\Facades\Phpclaw;
 Phpclaw::prohibitDangerousTools();   // e.g. in production
 ```
 
-They are allowed by default (like migration prohibition). Call `prohibit()` — typically in a production service provider — to disable them. File tools remain path-scoped via `PathResolver`. See [SECURITY.md](../SECURITY.md).
+They are **prohibited by default** — call `DangerousTools::allow()` (e.g. in a service provider, or only in trusted/local environments) to enable them. `prohibit()` / the facade re-locks them. File tools remain path-scoped via `PathResolver`. See [SECURITY.md](../SECURITY.md).
 
 ## Adding a tool
 

src/DangerousTools.php

@@ -8,7 +8,7 @@
 
 class DangerousTools
 {
-    protected static bool $prohibited = false;
+    protected static bool $prohibited = true;
 
     public static function allow(): void
     {

tests/Unit/DangerousToolsTest.php

@@ -5,7 +5,13 @@
 use Kevariable\PhpclawLaravel\DangerousTools;
 use Kevariable\PhpclawLaravel\Exceptions\DangerousToolsProhibitedException;
 
-it('allows by default and guards without throwing (happy path)', function () {
+it('ships prohibited by default (safety)', function () {
+    $default = (new ReflectionClass(DangerousTools::class))->getDefaultProperties()['prohibited'];
+
+    expect($default)->toBeTrue();
+});
+
+it('guards without throwing once allowed (happy path)', function () {
     DangerousTools::allow();
     DangerousTools::guard();