Add internal development webhook configuration

docs/ocsentinel-deployment.md

@@ -75,6 +75,13 @@ This writes:
 
 - `C:\ProgramData\OCSentinel\secrets\ocsentinel-upload-secret.dat`
 
+## Development Upload
+
+For the internal development environment, copy
+`config/ocsentinel-client.dev.example.json` to the installed client config
+path and use its HTTP webhook URL. Production clients must use the HTTPS
+configuration with the public Sentinel domain instead.
+
 ## Current Manual Release State
 
 As of July 16, 2026, the first manual release is already published:

docs/ocsentinel-n8n-contract.md

@@ -32,6 +32,10 @@ The webhook itself may be reachable only on the internal network. It does not
 require public access to the n8n editor or API. Every managed device must be
 able to reach the webhook URL over HTTPS.
 
+For the isolated development environment only, HTTP is permitted at
+`http://172.16.41.197:5678/webhook/ocsentinel-ingest`. Do not reuse this URL,
+the development shared secret, or a disabled-TLS configuration in production.
+
 1. `Webhook`: accept `POST` on the configured private URL.
 2. `Code`: reject a request if `X-ATN-Device`, `X-ATN-Timestamp`,
    `X-ATN-Nonce`, `X-ATN-Version`, `X-ATN-Payload-SHA256`, or