erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: Campaign N CLOSED - user-accepted; #260 closed; #262 filed

Browse source 
The acceptance session on Coldeve ran 20 portal transits with zero wedges and captured a real wire-loss recovery live (resend/s=1 nak-in=1 mid-session, converged net-final ledger, graceful logout) - the event class that permanently killed sessions before N1. #260 is closed on that evidence. The one unrelated observation (first-login run-on-the-spot until a recall reset, self-healed, not reproduced on relogin) is filed as #262 with hypotheses and the no-workaround rule restated. Campaign doc, roadmap, and CLAUDE.md pointers flipped to the closed record.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-07-29 17:48:45 +02:00
parent 5872826a13
commit 91d1d0d6f4
3 changed files with 54 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

51
docs/ISSUES.md
View file

@ -97,6 +97,41 @@ Copy this block when adding a new issue:
---
## #262 — Run-on-the-spot at first login: no displacement until a recall reset
**Status:** OPEN
**Severity:** MEDIUM (self-heals via any teleport; first-login only so far)
**Filed:** 2026-07-29 (Campaign N acceptance run 1 on Coldeve)
**Component:** login flow / local movement / physics readiness
**Symptom (user report):** on the first login of the acceptance session the
character animated running but did not move ("ran on the spot"); casting a
recall spell — i.e. the first server teleport/position reset — fixed it, and
movement was normal for the rest of a 20-teleport session. The second login
(same binary, minutes later) did not reproduce.
**Evidence:** `artifacts/coldeve-acceptance-20260729/
acceptance-run1-20teleports-1recovery.log` (local). The login reveal was
clean — generation 1 reached collision=True before world-visible — so the
reveal gate is not the culprit. The log shows a large first-position
recenter jump (169,180)→(135,102)@0x87660009. Not yet attributed.
**Hypotheses to test (in order):** (a) server-side position rejection until
the first ForcePosition — our AutonomousPosition stream may have been
ignored by ACE until a position reset (check whether early 0xF61C sends
flowed and what ACE echoed); (b) client physics landed before the walkable
was resident at the exact spawn cell (the run-on-spot presentation is what
a missing contact plane looks like); (c) a Campaign-N interaction is NOT
suspected (the transport ledger was clean at login) but rule it out by
checking the first minute's [net-out]/[net-tick] against the movement
input timeline.
**Next:** reproduce with `ACDREAM_PROBE_RESOLVE=1` + `ACDREAM_PROBE_NET=1`
on a fresh login; the resolve lines name the missing piece directly. Do NOT
add a workaround (no auto-recall, no synthetic position kick).
---
## #261 — Wire LinkStatusSnapshot.PacketLossPercentage from retail's formula
**Status:** OPEN
@ -121,14 +156,18 @@ and the indicator shows non-zero loss under `tools/run-connected-loss-gate.ps1`.
## #260 — Portal-network wedge: outbound actions die + native/GPU memory climbs
**Status:** FIX IMPLEMENTED 2026-07-29 — **Campaign N slices N0–N6 all
shipped and reviewed** (outbound resend `43e60a69`, inbound
**Status:** CLOSED 2026-07-29 — **Campaign N complete and user-accepted.**
Slices N0–N6 all shipped and reviewed (outbound resend `43e60a69`, inbound
sequence-aligned ISAAC `46d209d0`, retail ack cadence `0265cc42`, NAK
emission + reclaim `852a59e3`, the permanent loss gate `4e290f00`,
handshake/assembler hardening `f9c5e47e`). The loss gate observes real
injected loss recovering in both directions with the cipher ledger
converged. CLOSES when the user's Coldeve endurance session passes the
historic 15-minute wedge horizon. Original root-cause record below.
handshake/assembler hardening `f9c5e47e`). Acceptance: the user's Coldeve
session ran 20 portal transits with zero wedges, and the log captured a
REAL wire loss recovering live (`resend/s=1 nak-in=1` mid-session;
`[net-final] resends=1 nak-in=1 … cksum-fail=0 … nakset=0` — evidence at
`artifacts/coldeve-acceptance-20260729/`, local). The exact event that
permanently killed sessions two days earlier is now a sub-second
non-event. One unrelated first-login anomaly filed as #262. Original
root-cause record below.
([`docs/plans/2026-07-29-network-transport-campaign.md`](plans/2026-07-29-network-transport-campaign.md)).
The wedge is missing packet-loss recovery in BOTH directions: (a) no outbound
retransmission — ACE's `RequestRetransmit` lists are parsed and consumed