@plurnk/plurnk-service 3.3.0 → 4.0.0

package/.env.defaults

@@ -111,7 +111,7 @@ PLURNK_SERVICE_PROPOSAL_TIMEOUT_MS=
 PLURNK_SERVICE_EXEC_HOLD=
 # Maximum turn hold, ms; expiry lets the loop continue while the stream remains live.
 PLURNK_SERVICE_EXEC_HOLD_MS=300000
-# Concurrent EXEC producers per workspace; excess executions wait FIFO; -1 = unlimited.
+# Concurrent external EXEC producers per workspace; excess executions wait FIFO; -1 = unlimited.
 PLURNK_SERVICE_EXEC_CONCURRENCY=12
 # Live input delivery deadline, positive ms, including queued writes; expiry retires input, not the process.
 PLURNK_SERVICE_EXEC_INPUT_TIMEOUT_MS=10000

package/INSTALL.md

@@ -22,6 +22,12 @@ For an explicitly shared Linux daemon, the npm package includes an example
 executable paths, environment, and logs. Installing the package never installs
 or enables the unit.
 
+To reach the daemon from other machines on your network, set `PLURNK_HOST=0.0.0.0`
+and browse to any of its addresses; nothing else is required. To serve it beyond
+a network you trust, put it behind the example [nginx front](./plurnk.nginx.conf),
+which carries TLS, security headers, sign-in throttling and an optional allow-list
+and says which two settings the daemon needs behind it.
+
 | Resource | Default location |
 | --- | --- |
 | User configuration | `$XDG_CONFIG_HOME/plurnk/.env` (`~/.config/plurnk/.env`) |

package/README.md

@@ -21,7 +21,7 @@ The exact model-facing language and operation set are owned by
 
 ## Lifecycle model
 
-Workspace = the shared world (one filesystem + membership overlay). Worker = one actor and its history over that world. Loop = one queued-to-terminal unit of work within a worker. Turns continue until messages are answered, results observed, and held work settled; WAIT yields while work remains. NOTE retains working memory independently of lifecycle. Workers fork and message each other — many clients, many workers, one workspace.
+Workspace = shared resources, configuration, and an optional project folder. Worker = one actor and its history within a workspace. Loop = one queued-to-terminal unit of work within a worker. Turns continue until messages are answered, results observed, and held work settled; WAIT yields while work remains. NOTE retains working memory independently of lifecycle. Workers fork and message each other — many clients, many workers, one workspace.
 
 ## Integration
 
@@ -80,7 +80,7 @@ The daemon can emit OpenTelemetry traces and low-cardinality metrics through the
 
 ## What the model can see
 
-Plurnk sees what Git tracks or a `members` definition includes. The AGENTS.md policy path is injected separately as privileged policy, not as a file entry. A path admitted by neither source does not exist to the model and cannot be overwritten. Accepted creation is exclusive and never orphaned: it is Git-added or receives an inspectable exact pick. Creation defaults to `project_root`, can be disabled or expanded to the canonical namespace by operator policy, and only an explicit pick overrides Git ignore. Member edits remain proposal-gated; an outside-root member is read-only unless a pick grants it. This is a membership list, not a perimeter: an execution deliberately reaches past it, so its proposal policy — not the file surface — is where consent is asked. Details: SPEC {§scheme-address} ({§fs-namespace} through {§fs-world-state}).
+Plurnk sees what Git tracks or a `members` definition includes. The AGENTS.md policy path is injected separately as privileged policy, not as a file entry. A path admitted by neither source does not exist to the model and cannot be overwritten. Accepted creation is exclusive and never orphaned: it is Git-added or receives an inspectable exact pick. Creation defaults to `project_root`, can be disabled or expanded to the canonical namespace by operator policy, and only an explicit pick overrides Git ignore. Member edits remain proposal-gated; an outside-root member is read-only unless a pick grants it. This is a membership list, not a perimeter: an execution deliberately reaches past it, so its proposal policy — not the file surface — is where consent is asked. Details: SPEC {§scheme-address} ({§fs-namespace} through {§fs-resource-state}).
 
 ## Tests