terminal-pilot 0.0.40 → 0.0.42

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Poe Platform
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -168,7 +168,10 @@ class TerminalSession {
   press(key: TerminalKey): Promise<void>;
   send(raw: string): Promise<void>; // raw bytes / escape sequences
   signal(signal: string): Promise<void>;
-  waitFor(pattern: string | RegExp, options?: WaitForOptions): Promise<string>;
+  waitFor(
+    pattern: string | RegExp,
+    options?: { timeout?: number; scope?: "history" | "screen" }
+  ): Promise<string>;
   waitForExit(options?: { timeout?: number }): Promise<number>; // throws on timeout
   waitForQuiet(ms: number): Promise<void>;
   screen(): Promise<TerminalScreen>;
@@ -249,6 +252,15 @@ Typical fixture workflow:
 4. Assert with `screen()` or `history()`
 5. `close()` the session
 
+`waitFor(...)` searches captured output history by default. Use
+`waitFor(pattern, { scope: "screen" })` when command echoes or previous output could match before
+the expected interactive screen is visible.
+
+When launching an interactive program through `npm run`, npm can buffer printable raw keys such as
+`q` until `Enter` is pressed. Prefer launching the underlying executable directly for raw-key tests.
+If the npm wrapper is part of the behavior under test, use `Control+c` for teardown and treat
+printable-key delivery as npm-wrapper behavior rather than application behavior.
+
 Example fixture-based test:
 
 ```ts