You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,7 @@ Browser test execution rules:
112
112
- Major user flows MUST be covered by long Playwright scenarios that execute real browser interactions end to end.
113
113
- Major browser scenarios MUST capture screenshot artifacts under `output/playwright/`.
114
114
- Editor typing and latency fixes are not done until they are reproduced and cleared on the live dev-host editor with real keyboard input, not only synthetic input helpers or the static UI-test host.
115
+
- When the user reports an editor regression on a specific script or exact `/editor?id=...` URL, reproduce on that same live script before treating browser-suite results as sufficient.
115
116
- Editor surface changes must ship with real-browser checks for scroll behavior, floating toolbar dropdowns, and TPS section controls when those areas are touched; static component tests alone are not enough.
116
117
117
118
Do not override the production app runtime URL with `--urls` or random ports. Media permissions are origin-bound, so local development must stay on the stable launch-settings origin. If `dotnet run` fails because that port is already in use, stop the existing dev-server process instead of switching the app host to a new port. The browser-test harness is the exception: it must resolve a fresh dynamic loopback port and propagate the actual origin into Playwright `BaseURL` and permission grants.
@@ -345,6 +346,7 @@ Ask first:
345
346
- runtime dependencies fetched from random external sources instead of vendored release artifacts
346
347
- progress updates that talk about internal skill routing instead of the concrete repo change
347
348
- long exploratory work before producing the concrete vendored files the user explicitly asked for
349
+
- unexpected browser debugger pause hooks in the default dev launch profile; browser debugging must stay explicit opt-in
Copy file name to clipboardExpand all lines: docs/Features/EditorAuthoring.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,12 +66,13 @@ sequenceDiagram
66
66
- source edits refresh metadata, tree labels, preview overlay, and status
67
67
- metadata edits rewrite the persisted TPS document without surfacing YAML in the editor body
68
68
- typing stays local-first while autosave persists on a short debounce instead of every keystroke
69
-
- active typing temporarily shows the native textarea text layer while the highlight overlay catches up after a short idle window, keeping keystrokes off the full highlight rebuild path
70
69
- the styled TPS overlay remains visible while the real textarea owns caret and selection, so editing stays inline instead of switching to a plain-text mode
70
+
- highlight overlay refresh is coalesced to the next animation frame, so typing stays immediate without dropping the editor into a plain-text fallback state
71
71
- the highlight overlay subtree is JS-owned while Blazor keeps workflow state, preventing per-keystroke DOM diff churn and keeping browser typing responsive
72
72
- plain `input` events no longer force a page-wide Blazor render; sidebar, metadata rail, and status refresh only after draft analysis or explicit selection/navigation interactions
73
73
- selection interop stays off the keystroke path and runs only for caret/selection workflows that actually need toolbar anchoring or focus moves
74
74
- the source highlight and textarea share the same wrapping metrics, preventing caret/text drift on multiline editing
75
+
- segment and block header lines keep their styled header treatment even while the user is in a temporarily dirty edit state such as trailing text after `]` or an incomplete closing bracket
75
76
- the authoring surface exposes a single vertical scroll container so the editor body does not fight a nested shell scrollbar
76
77
- the floating selection toolbar emotion affordance opens a real TPS emotion picker instead of applying a single hardcoded wrap
77
78
- the top toolbar shows direct TPS structure insert actions for `##` segments and `###` blocks, with the same actions still available from the insert dropdown
@@ -83,6 +84,7 @@ sequenceDiagram
83
84
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.Core.Tests/PrompterLive.Core.Tests.csproj`
84
85
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.Tests/PrompterLive.App.Tests.csproj`
85
86
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.UITests/PrompterLive.App.UITests.csproj`
87
+
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.UITests/PrompterLive.App.UITests.csproj --no-build --filter "FullyQualifiedName~EditorTypingTests"`
86
88
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.UITests/PrompterLive.App.UITests.csproj --filter "FullyQualifiedName~EditorTypingTests|FullyQualifiedName~EditorSourceSyncTests|FullyQualifiedName~EditorInteractionTests"`
87
89
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.Tests/PrompterLive.App.Tests.csproj --filter "FullyQualifiedName~Editor"`
88
90
-`dotnet test /Users/ksemenenko/Developer/PrompterLive/tests/PrompterLive.App.UITests/PrompterLive.App.UITests.csproj --no-build --filter "FullyQualifiedName~Editor"`
0 commit comments