chore: record server diagnostics push

.project-docs/30-worklog/tasks/20260831-push-server-diagnostics-7c4e91a2.md

@@ -0,0 +1,43 @@
+# Task: Push server diagnostics branch
+
+## Identity
+
+- Task ID: 20260831-push-server-diagnostics-7c4e91a2
+- Mode: Feature
+- Branch: codex/20260830-wechat-attachment-correlation-9f3a2c-wechat-attachment-correlation
+- Worktree: /Users/inmanx/Documents/lwltAPI-worktrees/20260830-wechat-attachment-correlation-9f3a2c
+- Base commit: a3963ad0f629818edfa921261acfeb28dde9c9dd
+- Owner: codex
+- Status: Ready for integration
+
+## Scope
+
+- Push the existing, tested server-diagnostics feature branch to the configured `origin` remote and establish upstream tracking.
+- Preserve the exact local commits and publish them under the same feature-branch name.
+- Record and verify the remote ref without changing source code, canonical project memory, release artifacts, or deployment state.
+
+## Intent And Constraints
+
+- The requested operation authorizes a Git remote push only; it does not authorize merging, rebasing, force-pushing, changing `main`, deploying, restarting services, or mutating live systems.
+- Remote `main` advanced independently to `98282d1` and diverges from this branch at `7b5d855`; publish the feature branch as-is so later integration can reconcile the histories explicitly.
+- Push only to `origin` (`LWLT-AIBOT.git`), not the separately configured legacy repository.
+- Preserve the validated server-diagnostics payload commit `a3963ad0f629818edfa921261acfeb28dde9c9dd`.
+
+## Outcome
+
+- The current feature branch was published to the same-named branch on `origin` with upstream tracking.
+- Remote `main`, the legacy remote, deployment state, and live services were not changed.
+
+## Verification
+
+- `git fetch origin` completed and showed remote `main` at `98282d127c989a7e9ca1d688c9d3d2fadd73e8bc`.
+- Pre-push `git ls-remote --heads origin <feature-branch>` returned no existing branch, so the push creates a new remote feature ref rather than overwriting shared history.
+- After push, verify that the remote feature ref equals local `HEAD` and that branch upstream tracking points to the same `origin` ref.
+
+## Follow-ups
+
+- Integration or merge into `main` remains a separate, explicitly authorized task because the remote histories have diverged.
+
+## Promotion Candidates
+
+- None; this task publishes an existing feature branch and introduces no canonical project fact or behavior change.