From 8d8734ccf56e4d7d7d76527854bdc3c0179097ef Mon Sep 17 00:00:00 2001 From: hatayama Date: Mon, 24 Aug 2026 05:01:47 +0900 Subject: [PATCH 1/2] docs: explain HitSequence numbering and hot-reload's supported edit shapes Agents were treating HitSequence as 1..HitCount for one marker, and hot-reload --help only mentioned method bodies even though added members in the same file already work. The note and skill text now state both facts in the wording the plan locked. Co-authored-by: Cursor --- .agents/skills/uloop-hot-reload/SKILL.md | 2 +- .../skills/uloop-pause-point/references/captured-variables.md | 2 +- .claude/skills/uloop-hot-reload/SKILL.md | 2 +- .../skills/uloop-pause-point/references/captured-variables.md | 2 +- .../PausePoint/Skill/references/captured-variables.md | 2 +- Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md | 2 +- cli/common/tools/default-tools.json | 2 +- cli/dispatcher/shared-inputs-stamp.json | 2 +- cli/project-runner/internal/projectrunner/pause_point_wait.go | 2 +- .../internal/projectrunner/pause_point_wait_test.go | 4 ++-- cli/project-runner/shared-inputs-stamp.json | 2 +- 11 files changed, 12 insertions(+), 12 deletions(-) diff --git a/.agents/skills/uloop-hot-reload/SKILL.md b/.agents/skills/uloop-hot-reload/SKILL.md index cbe057438..6a1d58f98 100644 --- a/.agents/skills/uloop-hot-reload/SKILL.md +++ b/.agents/skills/uloop-hot-reload/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Apply method-body hot reload to edited C# sources in a running Unity Editor without domain reload. Use after small method edits when you need PlayMode/EditMode feedback without uloop compile." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." --- # uloop hot-reload diff --git a/.agents/skills/uloop-pause-point/references/captured-variables.md b/.agents/skills/uloop-pause-point/references/captured-variables.md index a03c0094b..3cda10527 100644 --- a/.agents/skills/uloop-pause-point/references/captured-variables.md +++ b/.agents/skills/uloop-pause-point/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. ## Caller frames diff --git a/.claude/skills/uloop-hot-reload/SKILL.md b/.claude/skills/uloop-hot-reload/SKILL.md index cbe057438..6a1d58f98 100644 --- a/.claude/skills/uloop-hot-reload/SKILL.md +++ b/.claude/skills/uloop-hot-reload/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Apply method-body hot reload to edited C# sources in a running Unity Editor without domain reload. Use after small method edits when you need PlayMode/EditMode feedback without uloop compile." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." --- # uloop hot-reload diff --git a/.claude/skills/uloop-pause-point/references/captured-variables.md b/.claude/skills/uloop-pause-point/references/captured-variables.md index a03c0094b..3cda10527 100644 --- a/.claude/skills/uloop-pause-point/references/captured-variables.md +++ b/.claude/skills/uloop-pause-point/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. ## Caller frames diff --git a/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md b/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md index a03c0094b..3cda10527 100644 --- a/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md +++ b/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. ## Caller frames diff --git a/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md b/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md index cbe057438..6a1d58f98 100644 --- a/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md +++ b/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Apply method-body hot reload to edited C# sources in a running Unity Editor without domain reload. Use after small method edits when you need PlayMode/EditMode feedback without uloop compile." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." --- # uloop hot-reload diff --git a/cli/common/tools/default-tools.json b/cli/common/tools/default-tools.json index 21faa7778..8223fec0b 100644 --- a/cli/common/tools/default-tools.json +++ b/cli/common/tools/default-tools.json @@ -754,7 +754,7 @@ }, { "name": "hot-reload", - "description": "Apply method-body hot reload to edited C# sources in a running Unity Editor without domain reload. Use after small method edits when you need PlayMode/EditMode feedback without uloop compile.", + "description": "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'.", "inputSchema": { "type": "object", "properties": { diff --git a/cli/dispatcher/shared-inputs-stamp.json b/cli/dispatcher/shared-inputs-stamp.json index 4d822fb97..91d795a31 100644 --- a/cli/dispatcher/shared-inputs-stamp.json +++ b/cli/dispatcher/shared-inputs-stamp.json @@ -1,4 +1,4 @@ { "schemaVersion": 1, - "sharedInputsHash": "9fed9a9a549f45ecc91e381f1c780dd4af0f212b" + "sharedInputsHash": "2db8de86e896d8fea1f540f80e44cc29b1004740" } diff --git a/cli/project-runner/internal/projectrunner/pause_point_wait.go b/cli/project-runner/internal/projectrunner/pause_point_wait.go index 7bee5e515..150c68e57 100644 --- a/cli/project-runner/internal/projectrunner/pause_point_wait.go +++ b/cli/project-runner/internal/projectrunner/pause_point_wait.go @@ -30,7 +30,7 @@ const ( // pausePointCapturedVariableHistoryNote explains why the latest hit is absent from // CapturedVariableHistory: repeating it would duplicate CapturedVariables. - pausePointCapturedVariableHistoryNote = "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables." + pausePointCapturedVariableHistoryNote = "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." // pausePointTraceStatusNote explains that a trace-mode Hit did not pause Play Mode. pausePointTraceStatusNote = "Trace mode does not pause Play Mode; Status 'Hit' records that the marker fired while the game kept running." diff --git a/cli/project-runner/internal/projectrunner/pause_point_wait_test.go b/cli/project-runner/internal/projectrunner/pause_point_wait_test.go index a9ea8f4ed..f53b09e54 100644 --- a/cli/project-runner/internal/projectrunner/pause_point_wait_test.go +++ b/cli/project-runner/internal/projectrunner/pause_point_wait_test.go @@ -1315,7 +1315,7 @@ func TestPausePointStatusResponseIncludesCapturedVariableHistoryNote(t *testing. if err := json.Unmarshal(rawNote, ¬e); err != nil { t.Fatalf("unmarshal note failed: %v", err) } - if note != pausePointCapturedVariableHistoryNote { + if note != "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." { t.Fatalf("CapturedVariableHistoryNote mismatch: got %#v, want %#v", note, pausePointCapturedVariableHistoryNote) } @@ -1925,7 +1925,7 @@ func TestRunPausePointStatusIncludesCapturedVariableHistoryNoteWhenLatestHitIsFi if err := json.Unmarshal(rawNote, ¬e); err != nil { t.Fatalf("unmarshal note failed: %v", err) } - if note != pausePointCapturedVariableHistoryNote { + if note != "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." { t.Fatalf("CapturedVariableHistoryNote mismatch: got %#v, want %#v", note, pausePointCapturedVariableHistoryNote) } diff --git a/cli/project-runner/shared-inputs-stamp.json b/cli/project-runner/shared-inputs-stamp.json index c540b0d53..a12c790d5 100644 --- a/cli/project-runner/shared-inputs-stamp.json +++ b/cli/project-runner/shared-inputs-stamp.json @@ -1,4 +1,4 @@ { "schemaVersion": 1, - "sharedInputsHash": "abce606e6b8233345a41199ba7c54c83b906ebb6" + "sharedInputsHash": "da2a5aa7cd11052b7eeacb3a9d75f68e91043742" } From b1443d37251bd7c26a375749d044375ba80705dd Mon Sep 17 00:00:00 2001 From: hatayama Date: Mon, 24 Aug 2026 05:11:46 +0900 Subject: [PATCH 2/2] docs: bound HitSequence to the Editor domain and stop denying signature reloads session-wide overstated lifetime because the counter resets on domain reload, and the hot-reload blurb contradicted the skill body by sending every signature change to compile. Tests now fail against a local wantNote so a drifted constant cannot hide in the diagnostic. Co-authored-by: Cursor --- .agents/skills/uloop-hot-reload/SKILL.md | 2 +- .../uloop-pause-point/references/captured-variables.md | 2 +- .claude/skills/uloop-hot-reload/SKILL.md | 2 +- .../uloop-pause-point/references/captured-variables.md | 2 +- .../PausePoint/Skill/references/captured-variables.md | 2 +- .../Editor/FirstPartyTools/HotReload/Skill/SKILL.md | 2 +- cli/common/tools/default-tools.json | 2 +- cli/dispatcher/shared-inputs-stamp.json | 2 +- .../internal/projectrunner/pause_point_wait.go | 2 +- .../internal/projectrunner/pause_point_wait_test.go | 10 ++++++---- cli/project-runner/shared-inputs-stamp.json | 2 +- 11 files changed, 16 insertions(+), 14 deletions(-) diff --git a/.agents/skills/uloop-hot-reload/SKILL.md b/.agents/skills/uloop-hot-reload/SKILL.md index 6a1d58f98..61edb6d31 100644 --- a/.agents/skills/uloop-hot-reload/SKILL.md +++ b/.agents/skills/uloop-hot-reload/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); it can also change signatures when the same reload covers the old signature's compiled callers. New types, or members other files must reference, require 'uloop compile'." --- # uloop hot-reload diff --git a/.agents/skills/uloop-pause-point/references/captured-variables.md b/.agents/skills/uloop-pause-point/references/captured-variables.md index 3cda10527..feb7320ae 100644 --- a/.agents/skills/uloop-pause-point/references/captured-variables.md +++ b/.agents/skills/uloop-pause-point/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker. ## Caller frames diff --git a/.claude/skills/uloop-hot-reload/SKILL.md b/.claude/skills/uloop-hot-reload/SKILL.md index 6a1d58f98..61edb6d31 100644 --- a/.claude/skills/uloop-hot-reload/SKILL.md +++ b/.claude/skills/uloop-hot-reload/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); it can also change signatures when the same reload covers the old signature's compiled callers. New types, or members other files must reference, require 'uloop compile'." --- # uloop hot-reload diff --git a/.claude/skills/uloop-pause-point/references/captured-variables.md b/.claude/skills/uloop-pause-point/references/captured-variables.md index 3cda10527..feb7320ae 100644 --- a/.claude/skills/uloop-pause-point/references/captured-variables.md +++ b/.claude/skills/uloop-pause-point/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker. ## Caller frames diff --git a/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md b/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md index 3cda10527..feb7320ae 100644 --- a/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md +++ b/Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/references/captured-variables.md @@ -92,7 +92,7 @@ For a self-progressing game, arranging a scenario through real input alone is a `await-pause-point`'s hit response also carries a top-level `Warning` (omitted when empty): it flags multiple hits, multiple matching logs, or truncated matching logs, so you can tell a single clean hit apart from evidence that needs closer inspection. Enable-time patch diagnostics (for example physics-callback cached dispatch) are not in `Warning`; on `enable-pause-point --await` they appear as `EnableTimeWarning` instead. `MatchingLogs` (log entries whose text contains the marker id) is still embedded, but source-derived ids rarely appear in log text, so treat `CapturedVariables` as the primary variable evidence. -Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker. +Use `Generation`, `EnabledAtUtc`, and the hit sequence fields from the hit or status response to tell a fresh marker from stale evidence with the same id. `RemainingMilliseconds` and `Expired` are returned directly so you do not need to infer marker lifetime from elapsed time. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker. ## Caller frames diff --git a/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md b/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md index 6a1d58f98..61edb6d31 100644 --- a/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md +++ b/Packages/src/Editor/FirstPartyTools/HotReload/Skill/SKILL.md @@ -1,7 +1,7 @@ --- name: uloop-hot-reload toolName: hot-reload -description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'." +description: "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); it can also change signatures when the same reload covers the old signature's compiled callers. New types, or members other files must reference, require 'uloop compile'." --- # uloop hot-reload diff --git a/cli/common/tools/default-tools.json b/cli/common/tools/default-tools.json index 8223fec0b..2b62932e4 100644 --- a/cli/common/tools/default-tools.json +++ b/cli/common/tools/default-tools.json @@ -754,7 +754,7 @@ }, { "name": "hot-reload", - "description": "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); new types, signature changes to existing methods, or members other files must reference require 'uloop compile'.", + "description": "Hot reload applies method-body edits and can add new methods and fields (added members are visible only to edited code in the same file); it can also change signatures when the same reload covers the old signature's compiled callers. New types, or members other files must reference, require 'uloop compile'.", "inputSchema": { "type": "object", "properties": { diff --git a/cli/dispatcher/shared-inputs-stamp.json b/cli/dispatcher/shared-inputs-stamp.json index 91d795a31..c2fd13c77 100644 --- a/cli/dispatcher/shared-inputs-stamp.json +++ b/cli/dispatcher/shared-inputs-stamp.json @@ -1,4 +1,4 @@ { "schemaVersion": 1, - "sharedInputsHash": "2db8de86e896d8fea1f540f80e44cc29b1004740" + "sharedInputsHash": "057220b1f49759a881862f4fcc38916b3d2bbcff" } diff --git a/cli/project-runner/internal/projectrunner/pause_point_wait.go b/cli/project-runner/internal/projectrunner/pause_point_wait.go index 150c68e57..ecd386c31 100644 --- a/cli/project-runner/internal/projectrunner/pause_point_wait.go +++ b/cli/project-runner/internal/projectrunner/pause_point_wait.go @@ -30,7 +30,7 @@ const ( // pausePointCapturedVariableHistoryNote explains why the latest hit is absent from // CapturedVariableHistory: repeating it would duplicate CapturedVariables. - pausePointCapturedVariableHistoryNote = "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." + pausePointCapturedVariableHistoryNote = "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker." // pausePointTraceStatusNote explains that a trace-mode Hit did not pause Play Mode. pausePointTraceStatusNote = "Trace mode does not pause Play Mode; Status 'Hit' records that the marker fired while the game kept running." diff --git a/cli/project-runner/internal/projectrunner/pause_point_wait_test.go b/cli/project-runner/internal/projectrunner/pause_point_wait_test.go index f53b09e54..62eafe3a3 100644 --- a/cli/project-runner/internal/projectrunner/pause_point_wait_test.go +++ b/cli/project-runner/internal/projectrunner/pause_point_wait_test.go @@ -1315,9 +1315,10 @@ func TestPausePointStatusResponseIncludesCapturedVariableHistoryNote(t *testing. if err := json.Unmarshal(rawNote, ¬e); err != nil { t.Fatalf("unmarshal note failed: %v", err) } - if note != "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." { + wantNote := "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker." + if note != wantNote { t.Fatalf("CapturedVariableHistoryNote mismatch: got %#v, want %#v", - note, pausePointCapturedVariableHistoryNote) + note, wantNote) } } @@ -1925,9 +1926,10 @@ func TestRunPausePointStatusIncludesCapturedVariableHistoryNoteWhenLatestHitIsFi if err := json.Unmarshal(rawNote, ¬e); err != nil { t.Fatalf("unmarshal note failed: %v", err) } - if note != "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a session-wide sequence shared by all pause points (they order hits across markers); they are not 1..HitCount for this marker." { + wantNote := "CapturedVariableHistory lists hits before the latest one; the latest hit's variables are in CapturedVariables. HitSequence numbers come from a sequence shared by all pause points in the current Editor domain (it resets on domain reload); they order hits across markers and are not 1..HitCount for this marker." + if note != wantNote { t.Fatalf("CapturedVariableHistoryNote mismatch: got %#v, want %#v", - note, pausePointCapturedVariableHistoryNote) + note, wantNote) } } diff --git a/cli/project-runner/shared-inputs-stamp.json b/cli/project-runner/shared-inputs-stamp.json index a12c790d5..736bf00f1 100644 --- a/cli/project-runner/shared-inputs-stamp.json +++ b/cli/project-runner/shared-inputs-stamp.json @@ -1,4 +1,4 @@ { "schemaVersion": 1, - "sharedInputsHash": "da2a5aa7cd11052b7eeacb3a9d75f68e91043742" + "sharedInputsHash": "9ac17f7fa800a193619ef4e1c5da9cd33f7f2259" }