client2server.dlog

@@ -0,0 +1,80 @@
+================================================================================
+client2server.dlog — deployment log
+================================================================================
+Project:     client2server
+Owner:       Luis Rosales
+Last update: 2026-06-17 19:14 EDT
+Last commit: 87f476d 2026-06-10 11:05:32 -0400 docs(MEMORY): document Lua 5.1 compatibility rule for all OpenWrt code
+Purpose:     Resume point after any session/model interruption. Read this
+             file first; it tells you where the work is, what's done,
+             what was tested, and what's next. Git history shows WHAT
+             changed; this file shows WHY and HOW to verify it.
+
+================================================================================
+STANDING RULE — DEPLOYMENT PROTOCOL  (binding for every session)
+================================================================================
+Rule:    Update this file at the END of every deployment. This is a
+        hard rule, not a suggestion. It applies to every session,
+        every model, every operator.
+
+What counts as a "deployment" (UPDATE the file):
+  • Code changes that pass tests and are committed
+  • Schema migrations (up OR down)
+  • New HTTP routes / new endpoints
+  • New UI features / new pages
+  • Smoke scripts that exercise real endpoints
+  • Bug fixes that change behavior
+  • Any change to a service binary's runtime behavior
+  • Config / env changes that affect runtime behavior
+
+What does NOT count (DO NOT update the file just for these):
+  • Documentation changes (README, comments, this file itself)
+  • Architecture decisions / plans / surveys
+  • Pure refactors with no behavior change
+  • Test-only changes that don't exercise new code paths
+  • Cosmetic UI tweaks that don't add a feature
+
+What an entry must contain:
+  1. Timestamp (EDT)
+  2. One-line summary of what shipped
+  3. Commit hash
+  4. Top-level files added/changed (paths only, not full diffs)
+  5. Tests run + result
+  6. Verification commands the next session can run
+  7. Known issues / next step
+
+Why:    Resume after any interruption — model crash, rate limit,
+        gateway restart, end of session — by reading THIS file
+        instead of analyzing the codebase. The first 40 lines
+        must be enough to know exactly where we are.
+
+When to update: at the END of the session, OR when an obvious
+                natural break appears (milestone shipped, smoke
+                verified). Never mid-implementation; wait until
+                the commit is in.
+
+================================================================================
+TL;DR — where we are right now
+================================================================================
+- Last commit: 87f476d 2026-06-10 11:05:32 -0400 docs(MEMORY): document Lua 5.1 compatibility rule for all OpenWrt code
+- .dlog created: 2026-06-17 19:14 EDT (backfilling the protocol)
+- See entries below for recent deployments.
+
+================================================================================
+ENTRY LOG  (most recent first; append new entries at the TOP of this block)
+================================================================================
+Pre-protocol history (last 3 commits before the .dlog was created):
+87f476d  2026-06-10 11:05:32 -0400  docs(MEMORY): document Lua 5.1 compatibility rule for all OpenWrt code
+ff7bf22  2026-06-10 11:03:44 -0400  Lua: fix line 1 syntax error that broke all of 5.1 compatibility
+2af96b0  2026-06-10 10:58:00 -0400  Buffering: unify hotplug + Lua through shared on-disk buffer
+Add a proper entry above this line for every deployment from now on.
+
+================================================================================
+ENTRY TEMPLATE  (copy this for each new deployment)
+YYYY-MM-DD HH:MM EDT  —  <one-line summary>
+Commit: <hash>
+Files:  <top-level paths added/changed>
+Tests:  <go test / pnpm test / smoke> → <result>
+Verify: <one or more commands the next session can run to confirm>
+Notes:  <known issues, follow-ups, or 'none'>
+================================================================================