Repository navigation
release: v0.1.0 - #6
Merged
Merged
Conversation
Task: US-IO-CLI-0.1.0-T01
Task: US-IO-CLI-0.1.0-T02
Task: US-IO-CLI-0.1.0-T03
Task: US-IO-CLI-0.1.0-T04
Task: US-IO-CLI-0.1.0-T05
Task: US-IO-CLI-0.1.0-T06
Task: US-IO-CLI-0.1.0-T07
Task: US-IO-CLI-0.1.0-T08
Task: US-IO-CLI-0.1.0-T09
Task: US-IO-CLI-0.1.0-T10
Task: US-IO-CLI-0.1.0-T11
Task: US-IO-CLI-0.1.0-T12
Task: US-IO-CLI-0.1.0-T13
Task: US-IO-CLI-0.1.0-T14
Task: US-IO-CLI-0.1.0-T15
Task: US-IO-CLI-0.1.0-T16
Task: US-IO-CLI-0.1.0-T17
Task: US-IO-CLI-0.1.0-T18
Task: US-IO-CLI-0.1.0-T19
F1 is the release's one manual criterion and it needs a clean first run: a throwaway workspace with something real to fix, a throwaway config home so the operator's own configuration is untouched, and no provider key in the environment, because the wizard's masked credential field is part of what the criterion exercises.
The viewport is a fixed few rows and a streaming answer commits each line to scrollback as it finishes, so a two-hundred-line answer leaves it the size it started. ratatui sets an inline viewport's height when the terminal is built and offers no way to change it, and rebuilding would re-query the cursor and risk shifting the scrollback this product exists to protect. These three files were modified while US-IO-CLI-0.1.0-T12 was in flight but were not in that task's declared files list, so the checkpoint that commits a task's own files did not stage them. Every CI run since then was green against a tree that had neither the change nor the tests for it, which is exactly why the commit protocol says to read the staged list rather than trust it.
Task: US-IO-CLI-0.1.0-T19
Task: US-IO-CLI-0.1.0-T19
Task: US-IO-CLI-0.1.0-T19
Splitting the wizard onto its own taller viewport means attaching the terminal twice, and the keyboard thread had been moved ahead of the first attach. Placing an inline viewport asks the terminal where its cursor is and reads the answer back off stdin, so a thread sitting in crossterm::event::read() consumed it and the query timed out — the binary refused to start, with the error added for exactly this case pointing at the terminal rather than at us. The reader now polls instead of blocking, so it can be told to stand down and joined; it starts only once a screen is attached and stops before the next attach. Keyboard::start takes the attached screen as a witness argument, which makes the ordering a compile error to get wrong rather than a comment asking politely. Caught by the owner running the binary; no test in the suite reaches the driver's own startup ordering.
feat: io-cli 0.1.0 — the inline terminal interface over io-harness
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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
2 participants
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.
Summary
io-cli 0.1.0 — the first release. A terminal interface over io-harness that renders run events, edits a prompt and reads a keyboard, and contains no agent loop, provider client, tool, sandbox, policy engine or session store of its own.
The record is sealed and pinned:
io-cli/0.1.0: sha256:e25f9954….Type
feat
Target branch
develop→mainrelease PR (release: v0.1.0)Changelog
CHANGELOG.mdcarries the## [0.1.0]section, which is whatrelease.ymlreads for the Release notes.Checklist
Notes for the reviewer
Gates re-measured on the shipped tree at
9349aa0;develop's tree is identical to the gated one. CI green on macOS, Linux and Windows plus lint and msrv. All four release targets were proved to cross-compile and package on a throwaway branch before the tag depended on them.The tag
v0.1.0is pushed alone after this merge; that is what cuts the Release and attaches the four artifacts andSHA256SUMS.