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: docs/next-steps.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,3 +18,19 @@ Focused follow-up work for `@knighted/develop`.
18
18
- Ensure the deterministic lane still exercises the same user-facing flows (render, typecheck, lint, diagnostics drawer/button states), only swapping the source of runtime artifacts.
19
19
- Suggested implementation prompt:
20
20
- "Add a deterministic E2E execution mode for `@knighted/develop` that serves pinned runtime artifacts locally (instead of live CDN fetches) and wire it into CI as a required check on every PR. Keep a separate lightweight CDN-smoke E2E check for real-network coverage. Validate with `npm run lint`, deterministic Playwright PR checks, and one CDN-smoke Playwright run."
21
+
22
+
4.**Issue #18 continuation (resume from Phase 2)**
23
+
- Continue the GitHub AI assistant rollout after completed Phases 0-1:
- Phase 2: chat drawer UX with streaming responses first, plus non-streaming fallback.
28
+
- Add selected repository state plumbing now so Phase 4 (PR write flow) can reuse it.
29
+
- Add README documentation for fine-grained PAT setup (reuse existing screenshots referenced in docs/byot.md).
30
+
- Keep behavior and constraints aligned with current implementation:
31
+
- Keep everything behind the existing browser-only AI feature flag.
32
+
- Preserve BYOT token semantics (localStorage persistence until user deletes).
33
+
- Keep CDN-first runtime behavior and existing fallback model.
34
+
- Do not add dependencies without explicit approval.
35
+
- Suggested implementation prompt:
36
+
- "Continue Issue #18 in @knighted/develop from the current Phase 1 baseline. Implement Phase 2 by adding a separate AI chat drawer with streaming response rendering (primary) and a non-streaming fallback path. Wire selected repository state as shared app state for upcoming Phase 4 PR actions. Update README with a concise fine-grained PAT setup section that links to existing BYOT screenshot assets/docs. Keep all AI/BYOT UI and behavior behind the existing browser-only feature flag, preserve current token persistence and repo filtering behavior, and validate with npm run lint plus targeted Playwright coverage for chat drawer visibility, streaming/fallback behavior, and repo-context selection plumbing."
0 commit comments