arrival-points-acceptance.json
docs/evidence/arrival-points-acceptance.json
1{
2 "capability": "Named arrival points with creator preview and shared gateway position/facing",
3 "approximate_full_plan_percent": 59,
4 "headless": {
5 "passed": 587,
6 "failed": 0,
7 "evidence": "arrival-points-headless.tap",
8 "command": "node --import tsx --test --test-concurrency=4 tests/*.test.ts",
9 "scope": "Complete suite after final schema/authoring/native changes. Subsequent worker arrival-sequence metadata was checked by final typecheck and both production-browser workflows."
10 },
11 "checks": [
12 "TypeScript and package boundaries: 119 source files",
13 "Arrival references, 16-point catalog budget, coordinate/facing bounds and historical compiler identities",
14 "Stable command replay and exact source undo across multiple point removals and gateway unlinking",
15 "Creating a place containing arrival points promotes format and records its format conflict key",
16 "Native position and heading on travel, grounded floor, exact checkpoint restore and exact occupant preservation during revision fork",
17 "Workflow YAML parsed; independent creator jobs have unique artifact names"
18 ],
19 "browser": {
20 "arrivals": {
21 "stats": {
22 "startTime": "2026-10-25T11:54:43.371Z",
23 "duration": 47670.492999999995,
24 "expected": 1,
25 "skipped": 0,
26 "unexpected": 0,
27 "flaky": 0
28 },
29 "cases": [
30 {
31 "title": "named arrival editing controls two travelers positions and headings without moving current occupants",
32 "status": "expected",
33 "results": [
34 {
35 "status": "passed",
36 "duration": 44626
37 }
38 ]
39 }
40 ]
41 },
42 "places_regression": {
43 "stats": {
44 "startTime": "2026-10-25T11:55:36.327Z",
45 "duration": 42230.679,
46 "expected": 1,
47 "skipped": 0,
48 "unexpected": 0,
49 "flaky": 0
50 },
51 "cases": [
52 {
53 "title": "two travelers explore a live-added place, occupied removal is rejected, and undo restores the round trip",
54 "status": "expected",
55 "results": [
56 {
57 "status": "passed",
58 "duration": 39299
59 }
60 ]
61 }
62 ]
63 },
64 "commands": [
65 "npm run test:browser:arrivals",
66 "npm run test:browser:places"
67 ],
68 "environment": "Separate isolated production relays, CI=1, Chromium/SwiftShader; run serially after headless suite",
69 "screenshots": [
70 "arrival-controls.png",
71 "arrival-marker.png",
72 "gateway-arrival.png",
73 "arrival-shared.png"
74 ],
75 "verified": [
76 "Creator point preview leaves saved source unchanged",
77 "Both travelers land at x=1,z=3 with heading pi, and forward movement follows that heading",
78 "Arrival edit to x=-1 and heading pi/2 does not teleport current occupants; browser checks use 1 mm tolerance for contact settling",
79 "Saved Undo/Redo restores the point across editor reload",
80 "Both travelers return and cross again to the revised arrival",
81 "Linked point deletion rejected in creator UI",
82 "Traveler identities and connected status retained; no page errors",
83 "Previous place creation, occupied removal, deletion and Undo round trip still pass"
84 ]
85 },
86 "initial_failures": [
87 {
88 "case": "Schema coverage",
89 "cause": "New command increased the expected count from 24 to 25; corrected test expectation."
90 },
91 {
92 "case": "Additional creation/budget fixtures",
93 "cause": "New fixture initially included a forbidden empty groups array; oversized arrival fixture also removed an already-referenced point and hit the dangling-link check first. Corrected the fixtures to isolate their intended contracts; final full suite passed."
94 },
95 {
96 "case": "Occupant browser equality",
97 "observed": "Contact settling changed y by about 0.0001001 m and x by about 0.0000003 m. Exact native revision preservation already passed.",
98 "correction": "Use a 0.001 m browser position tolerance while retaining exact native checks; no production movement or timeout changes."
99 },
100 {
101 "case": "Two world-creation scenarios in one relay",
102 "observed": "Second scenario saved a different world while the first scenario development room remained active; clients correctly retained revision 5 instead of applying incompatible revision 7.",
103 "correction": "Run the standalone creator commands with separate test servers and give each its own CI matrix job. Both final workflows passed independently."
104 }
105 ],
106 "limits": [
107 "Creator positions require clear solid ground; no automatic floor or clearance placement",
108 "Lightweight saves do not retain named-arrival facing; native checkpoints do",
109 "No streaming, visual portals or server-authoritative/cross-host crossing transactions",
110 "No numbered roadmap milestone closed; character artwork deferred"
111 ],
112 "remote_ci": "New coverage configured; remote result not asserted by this local acceptance record"
113}
114