broad-announce/broad-announce.dlog

================================================================================
broad-announce.dlog — deployment log
================================================================================
Project:     broad-announce
Owner:       Luis Rosales
Last update: 2026-06-17 19:14 EDT
Purpose:     This is the canonical project log. Entries here point to
             milestone-specific .dlog files for the rich narrative; this
             file is the table of contents and the project-wide
             standing rule.

================================================================================
STANDING RULE — DEPLOYMENT PROTOCOL  (binding for every session)
================================================================================
Rule:    Update this file (or the relevant milestone .dlog) 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
  5. Tests run + result
  6. Verification commands
  7. Known issues / next step

When to update: at the END of the session, OR when an obvious natural
                break appears. Never mid-implementation.

================================================================================
MILESTONE LOGS  (richer, narrative-style)
================================================================================
The actual deployment entries live in milestone-specific files.
This file is the index. Add a row here when you create a new
milestone .dlog.

  M13b.dlog   — M13b (admin UI).  W0 + W1 shipped; W2 (Sources)
                and W3 (Telegram bot) next.  See M13b.dlog for the
                full status, files, tests, and verify commands.

================================================================================
ENTRY LOG  (most recent first; append new entries at the TOP of this block)
================================================================================
[Cross-cutting deployments only. Milestone-specific entries live in
the milestone .dlog referenced above. Add a row here only when a
deployment spans milestones or is workspace-meta (e.g. adopting the
.dlog protocol itself).]

2026-06-17 19:14 EDT  —  .dlog protocol adopted workspace-wide
Commit: this commit (broad-announce.dlog created + this index)
Files:  broad-announce.dlog (new), M13b.dlog (existing),
        DEPLOYMENT_LOG.md (workspace root), MEMORY.md (workspace root)
Tests:  n/a (protocol setup, not a code change)
Verify: cat /root/.openclaw/workspace/DEPLOYMENT_LOG.md
        cat broad-announce.dlog
        cat M13b.dlog
Notes:  Per the new rule, M13b.dlog entries are the deployment log
        for M13b work. broad-announce.dlog is the project index.
        Future milestones (M14, M15, etc.) should get their own
        <milestone>.dlog with a row added above.

================================================================================
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'>
================================================================================