M13b.dlog: add standing deployment rule + entry template

This is a documentation/protocol change, not a deployment. It
sets up the rule that subsequent deployments must log an entry
in this file. Future-me (or a fresh session after an interruption)
will read the top of the file, see the rule, and follow it.

Rule:  Update M13b.dlog at the end of every deployment. Skip
       for pure docs/architecture/test-only changes.

Template + first entry are at the bottom of the file.

M13b.dlog

@@ -10,6 +10,49 @@ Purpose:   Resume point after any session/model interruption. Read this
            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 deliverd-*, routerd, archiverd, ingestd, authd, admind
+  • 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 (use the template at the bottom):
+  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 (go test / pnpm test / smoke)
+  6. Verification commands the next session can run
+  7. Known issues / next step
+
+Why:    Luis needs to 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
 ================================================================================
@@ -20,7 +63,7 @@ TL;DR — where we are right now
   All tests green. Smoke script written but not yet run E2E (needs stack).
 - M13b W2 (Sources CRUD) and W3 (Telegram bot CRUD) are next.
 
-If you only have 60 seconds: read the "W1 in flight" block at the bottom.
+If you only have 60 seconds: read the W1 block below; everything before it is in production.
 
 ================================================================================
 W0 — SPA shell + embed into admind   [SHIPPED]
@@ -243,3 +286,39 @@ To pick up W2:
      still render ComingSoon — replace them the same way as
      web/src/routes/companies.tsx
 
+================================================================================
+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'>
+
+================================================================================
+ENTRY LOG  (most recent first; append new entries at the TOP of this block)
+================================================================================
+2026-06-17 18:44 EDT  —  W1 Companies CRUD shipped + this .dlog created
+Commit: c5e15f7 (W1), 63202f2 (.dlog creation)
+Files:  internal/authd/tenants.{go,_test.go}, cmd/authd/tenants.go,
+        cmd/authd/main.go (routes wired),
+        migrations/010_tenants_fields.{up,down}.sql,
+        web/src/features/companies/*.{ts,tsx},
+        web/src/components/ui/{badge,dialog,textarea,table,empty-state}.tsx,
+        web/src/lib/scope.ts, web/src/routes/companies.tsx,
+        web/tests/companies.test.tsx,
+        scripts/m13b_w1_smoke.sh,
+        M13b.dlog
+Tests:  go build/vet ./... clean; go test -count=1 ./... 22/22 ok;
+        pnpm run test 8/8 ok; pnpm run build clean;
+        migrations apply + roll back cleanly on PG 17
+Verify: cd /root/.openclaw/workspace/broad-announce
+        go test -count=1 ./...  &&  cd web && pnpm run test
+        bash -n scripts/m13b_w1_smoke.sh   (syntax only; needs live stack)
+        psql -f migrations/009_auth.up.sql
+        psql -f migrations/010_tenants_fields.up.sql
+Notes:  Smoke script not yet run E2E (requires running authd + Postgres).
+        W2 (Sources) and W3 (Telegram bot) are next.
+        Test for sort + order; the W1 test caught a real bug in
+        looksLikeEmail and formatDate (both fixed).