tula v0.1.2 - #14
Merged
Merged
tula v0.1.2#14
Conversation
`/update install` pulled the same tens of megabytes `install.sh` does and awaited the whole body in one `arrayBuffer()`, so the status line read `working` for all of it — the hang the installer had just stopped looking like, in the one place tula replaces its own binary. The body is read in chunks and the line counts them off, throttled so Ink is not repainted on every chunk, and falling back to bytes alone where the asset host sends no length. The callback is threaded the way `session.onProgress` already was rather than through a second mechanism, and only the archive is reported on: a meter for a 386-byte checksum file is a flicker naming work that is already done. The banner's working-directory line made that block four rows where the hero frame on the site could hold three, and the frame is anchored to its bottom and clipped at the top — so the row it dropped was the one naming the tool. The frame is a row deeper. Its own test was measuring a shape rather than the value: a checkout deep enough to be elided starts that line with an ellipsis instead of a tilde, so the assertion passed or failed on where the repository happened to be cloned, and it now asserts against `homeRelative` itself. Section labels — the heading above every block on every page — were drawn at 3.05:1, below the 4.5 that text that size needs, and so were the curl flag legend, the line telling a reader to read the script before piping it into a shell, and what enforces each promise on the security page. They take the grey the prose does, which passes at 5.26. The copy button was 22px and the footer links 21, under the 24 a target needs: the button's tap area reaches past the chip without the chip moving, since the title bar is drawn around it. At 200% text zoom the install page had begun scrolling sideways on a channel tab that could not wrap and an environment variable that is one unbreakable word. The only thing still drawn faint is the transcript inside a frame, which is a picture of dim terminal output; there is no third step that passes AA without becoming the second one, and the token says so. An `apple-touch-icon`, so an iOS home screen gets the mark rather than a screenshot — from a route with the extension in its name, because Next's own convention writes the file without one and a static host then serves an image as a byte stream, which is why `og.png` is a route too. The 404 no longer claims the front page as its canonical. The pre-commit skill gains the three checks this pass was missing: the site's SEO, whether it works on a phone, and whether the artifacts a release would ship actually run — a suite that passes against a faked `fetch` never streamed, and streaming was where the bug was. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
/update installpulled the same tens of megabytesinstall.shdoes and awaited the whole body in onearrayBuffer(), so the status line readworkingfor all of it — the hang the installer had just stopped looking like, in the one place tula replaces its own binary. The body is read in chunks and the line counts them off, throttled so Ink is not repainted on every chunk, and falling back to bytes alone where the asset host sends no length. The callback is threaded the waysession.onProgressalready was rather than through a second mechanism, and only the archive is reported on: a meter for a 386-byte checksum file is a flicker naming work that is already done.The banner's working-directory line made that block four rows where the hero frame on the site could hold three, and the frame is anchored to its bottom and clipped at the top — so the row it dropped was the one naming the tool. The frame is a row deeper. Its own test was measuring a shape rather than the value: a checkout deep enough to be elided starts that line with an ellipsis instead of a tilde, so the assertion passed or failed on where the repository happened to be cloned, and it now asserts against
homeRelativeitself.Section labels — the heading above every block on every page — were drawn at 3.05:1, below the 4.5 that text that size needs, and so were the curl flag legend, the line telling a reader to read the script before piping it into a shell, and what enforces each promise on the security page. They take the grey the prose does, which passes at 5.26. The copy button was 22px and the footer links 21, under the 24 a target needs: the button's tap area reaches past the chip without the chip moving, since the title bar is drawn around it. At 200% text zoom the install page had begun scrolling sideways on a channel tab that could not wrap and an environment variable that is one unbreakable word. The only thing still drawn faint is the transcript inside a frame, which is a picture of dim terminal output; there is no third step that passes AA without becoming the second one, and the token says so.
An
apple-touch-icon, so an iOS home screen gets the mark rather than a screenshot — from a route with the extension in its name, because Next's own convention writes the file without one and a static host then serves an image as a byte stream, which is whyog.pngis a route too. The 404 no longer claims the front page as its canonical.The pre-commit skill gains the three checks this pass was missing: the site's SEO, whether it works on a phone, and whether the artifacts a release would ship actually run — a suite that passes against a faked
fetchnever streamed, and streaming was where the bug was.