CodingWorkspace

All Implemented Interfaces:
```
public class CodingWorkspace

                    
```
Central resolution of the coding workspace for Browser4's self-coding capability (the coding_* tools and the CLI code command family).
The workspace root defaults to the backend JVM working directory (user.dir), which is the runtime bundle directory when the server is launched by the CLI daemon — usually NOT where the user's code lives. Point it at a real repository with:
```
-Dbrowser4.agent.workspace=<path>                              (JVM system property)
BROWSER4_SERVER_OPTS=-Dbrowser4.agent.workspace=<path> ...     (CLI daemon env var)
```
When no explicit workspace is configured and the JVM working directory (or any of its parents) sits inside a Browser4 source checkout — a directory containing both ROOT.md and pom.xml, the same marker the CLI daemon uses — the repository root is used automatically. This makes the coding_* tools (and the browser4 code CLI family) operate on the user's code instead of the runtime bundle directory, so repo-relative paths like VERSION, browser4-plugins/..., and Maven module paths resolve correctly during self-development.
Related switches:
- browser4.agent.allowExternalAccess=true — permit absolute paths outside the workspace root (off by default).
- browser4.agent.allowDestructive=false — deny rm/del/mv/cp/kill style operations (on by default).

Nested Class Summary

Nested Classes
Modifier and Type	Class	Description

Field Summary

Fields
Modifier and Type	Field	Description
`private final Path`	`workspaceRoot`
`private final Boolean`	`allowExternalAccess`
`private final Boolean`	`allowDestructive`
`public final static CodingWorkspace`	`INSTANCE`

Constructor Summary

Constructors
Constructor	Description

Enum Constant Summary

Enum Constants
Enum Constant	Description

Method Summary

Modifier and Type	Method	Description
`final Path`	`findRepoRootFrom(Path start)`	Walk up from start looking for a Browser4 repository root — a directory containing both `ROOT.md` and `pom.xml` (the same marker the CLI daemon's `find_browser4_root` uses).
`final Path`	`getWorkspaceRoot()`	The workspace root for all coding file operations.
`final Boolean`	`getAllowExternalAccess()`	Whether absolute paths outside the workspace root are permitted.
`final Boolean`	`getAllowDestructive()`	Whether destructive file operations (delete/move/copy) are permitted.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
- Method Detail
  - findRepoRootFrom
```
 final Path findRepoRootFrom(Path start)
```
    Walk up from start looking for a Browser4 repository root — a directory containing both ROOT.md and pom.xml (the same marker the CLI daemon's find_browser4_root uses). Returns null when no repository root is found (e.g. a globally installed runtime).
  - getWorkspaceRoot
```
 final Path getWorkspaceRoot()
```
    The workspace root for all coding file operations.
    Computed on every access (not cached) so tests and runtime reconfiguration can switch the property.
  - getAllowExternalAccess
```
 final Boolean getAllowExternalAccess()
```
    Whether absolute paths outside the workspace root are permitted.
  - getAllowDestructive
```
 final Boolean getAllowDestructive()
```
    Whether destructive file operations (delete/move/copy) are permitted.