WIP: run CI on the accumulated agent work (does the APK build?) - #1
Merged
Merged
Conversation
added 3 commits
September 10, 2026 17:44
This is a WIP checkpoint, NOT a verified build. The tree does not typecheck: app/src/main/kotlin/app/pi/ui/chat/ChatSheets.kt and ChatScreen.kt reference a 'QueueMode' that the GUI agent is still writing. Committed only so the work survives a session interruption — main is deliberately left at e8bffc0 and this branch is not for merging until every agent has landed and the frozen tree passes tools/typecheck.sh and :rpc:test. What is in here, by producer: - syntax highlighting: a pi extension serving the real highlight.js 10.7.3 over loopback plus the Kotlin client (verified 56/56 against pi's own renderer), and no new dependencies - adversarial fidelity review (docs/fidelity-review.md) and extension compatibility audit (docs/extension-compatibility.md) - syntax-highlight backend evaluation (docs/syntax-highlight-eval.md, marked superseded at the top) - package/trust layer, markdown gaps, RPC command surface, GUI surfaces: all mid-write - docs/known-gaps.md and docs/feature-gaps.md-adjacent notes - fix: the a11y description string resource, the two runtime-assembly bugs, and an unclosed KDoc comment I introduced myself
The GUI agent reports typecheck: OK and lists the pi source files it read for each area. Contains the slash palette, session management + tree, model and thinking pickers, queue/compaction/retry toggles, bash mode, session stats, and the 'TUI-only, say so honestly' handling. Four handoffs to other agents are recorded: rpc/Events.kt still lacks extensionPath and MessageEnd.customType; engine/** has no restart entry, so /reload cannot be replaced in the GUI; runtime/** has no trust store. Still WIP: three agents are mid-write (markdown, packages, gate relaxation). This branch opens a PR so CI builds an APK without main carrying unverified work.
…ess lessons Adds three sections to docs/known-gaps.md: E (unassigned, no owner): tool-name conflicts between our three built-in extensions and user-installed ones (pi is first-registered-wins, so one side fails silently); whether the highlighter's attach(context) is ever actually called (if not, highlighting silently stays monochrome and the symptom points at the wrong thing); attachment input (the protocol has supported prompt.images all along, the app has no UI); @ file mentions; lazy engine boot plus browsing sessions without an engine; the ASSET_VERSION content fingerprint; built-in vs user-installed grouping in the extension manager; and the terminal build-vs-buy record, which never existed. F (limits, not todos): extension load failures are silent because pi only writes runtime.diagnostics; setLabel / tool-set / getSystemPrompt / load diagnostics have no RPC command at all; the TUI-only surfaces are no-ops in pi's own RPC mode. G (handed off, owner named) and H (process lessons): record != assign, which is why two rounds of 'is anything missing?' each turned up real items; clean file ownership cut an ownerless hole around the one file every feature calls; the delegation template must forbid all git write commands, not just commit/push, because checkout/reset/stash/clean can silently destroy every agent's work at once; and a red tree caused by a peer's half-written file is not evidence.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft PR opened purely to make CI run: the workflow triggers on pushes to main and on pull requests, and main must not carry unverified work.
The tree typechecks (
tools/typecheck.sh-> OK) but has never been resource-checked, so this is the first real test of whether an APK with the runtime payload assembles.Known: three agents are still mid-write (markdown gaps, package/trust layer, permission-gate relaxation), so later commits will follow. Do not merge.