Revert "documentation and file organization updates"

.github/workflows/test.yml

@@ -64,7 +64,7 @@ jobs:
         run: forge test --offline -vvv
 
   packages:
-    name: Kernel packages and production node
+    name: Package build freshness
     runs-on: ubuntu-latest
     permissions:
       contents: read
@@ -90,9 +90,3 @@ jobs:
 
       - name: Verify package build output is fresh
         run: git diff --exit-code -- packages
-
-      - name: Install production node dependencies
-        run: npm --prefix node/production ci --ignore-scripts
-
-      - name: Test production node
-        run: npm --prefix node/production test

.gitignore

@@ -30,8 +30,3 @@ agent/node_modules
 agent-library/agents/**/.swap-state*.json
 agent-library/agents/**/config.local.json
 agent/.state/
-
-# Production node local configuration, keys, state, and deployment broadcasts
-node/production/config.local.json
-node/production/.state/
-contracts/broadcast/

README.md

@@ -56,7 +56,6 @@ The copied `default` module now starts as a minimal standard scaffold using the
 - Agent module layout and new-commitment workflow: `agent-library/README.md`
 - Runner config, message APIs, publication nodes, and harness usage: `agent/README.md`
 - Standalone node daemons and startup commands: `node/README.md`
-- Oya production node, Logger deployment, and local end-to-end smoke: `node/production/README.md`
 - Deployment and configuration: `docs/deployment.md`
 - Signer options and `with-signer` helper: `docs/signers.md`
 - Offchain agent usage: `docs/agent.md`

contracts/README.md

@@ -60,21 +60,3 @@ This snapshot excludes randomized fuzz cases so gas comparisons use fixed inputs
 Tests run in Forge's local EVM without an RPC endpoint or private key. The first build may download the pinned compiler; subsequent tests run offline. `--offline` also avoids optional signature lookups that can trigger a Foundry 1.5.1 macOS proxy-settings crash inside a sandbox. Generated `out/` and `cache/` directories are ignored. See [`logger-execplan.md`](logger-execplan.md) for implementation decisions and validation evidence.
 
 See [AGENTS.md](AGENTS.md) for local agent instructions and [CONTRIBUTING.md](../CONTRIBUTING.md) for the shared contributor workflow.
-
-## Deploy Logger
-
-[`script/DeployLogger.s.sol`](script/DeployLogger.s.sol) deploys Logger and requires an explicit expected chain ID. Load `LOGGER_DEPLOYER_PK` securely into the environment, set `LOGGER_CHAIN_ID` to the target network ID, and set `LOGGER_RPC_URL` to its RPC endpoint. The deployer needs native currency for deployment gas. From the repository root, simulate first:
-
-```sh
-forge script --root contracts contracts/script/DeployLogger.s.sol:DeployLogger --rpc-url "$LOGGER_RPC_URL" --offline
-```
-
-After checking the intended chain and simulation, deploy:
-
-```sh
-forge script --root contracts contracts/script/DeployLogger.s.sol:DeployLogger --rpc-url "$LOGGER_RPC_URL" --broadcast --offline
-```
-
-The script rejects a chain that differs from `LOGGER_CHAIN_ID`. Record the contract address and successful receipt from `contracts/broadcast/DeployLogger.s.sol/<chainId>/run-latest.json`; reuse that address in the node's `loggerContract` config. Each fresh deployment creates another Logger. `--offline` disables compiler downloads, not RPC access, so run the build first.
-
-For a complete local deployment plus signed-message/IPFS/Logger verification, run `npm --prefix node/production run smoke:local` after following the [production node setup](../node/production/README.md). This deploys only to its isolated Anvil chain (31337), using generated local accounts.

node/README.md

@@ -2,8 +2,6 @@
 
 `node/` is the primary home for standalone Oya node daemons.
 
-The Oya production runtime lives in [`production/`](production/README.md). It installs independently, accepts signed messages over HTTP, publishes to IPFS, and logs CIDs through the hardened kernel packages, with durable transaction recovery. See its guide for setup and local end-to-end deployment. The experimental daemons described below use the earlier shared agent infrastructure.
-
 These daemons are separate from the commitment-serving agent loop in `agent/`:
 
 - the message publication node archives signed agent-authored messages to IPFS