Repository navigation
docs: close the project at the public alpha, with a mark and badges - #21
Merged
Merged
Conversation
The documents still promised a Beta, an x86_64 cloud run and a first release, and the threat model said its assumptions were not yet observed on a real host. - say which assumptions the ARM64 host showed, and that others are unverified - keep Beta and 1.0 as definitions only, with no work towards them planned - record the deleted test VM and the archived dogfood repository - drop release promises from installation and the security policy
The README opened on plain text, with no sign of CI state or licence, and explained the slice and the runners only in prose. - add the swarea mark, cut by the organisation rule from its source card - show the check workflow, the public-alpha status and the MIT licence - draw the slice, the runners and what each runner cannot see
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Why
RunnerSlice's development ends at the public alpha. The documents still promised:
The threat model still said its assumptions had yet to be observed on a real host. The README had no mark and no visible CI or licence state.
What changed
contract.md, with "no work towards them is planned".SECURITY.md.swarea-cyan-deep-0f6b7dby the organisation's mark rule. The source card is beside the mark indocs/assets/.checkworkflow, the public-alpha status, and the MIT licence.How it was verified
tests/run.shwith shellcheck 0.10.0. 20 scripts are clean, and 545 drill cases pass, 0 failed. The docs drill checks links, keys and spelling.#f7f7f6inside.quiet,mori-lensandvm-app-windowing.make-mark.html's draw of the card, run in Chrome.gatecheck.Evidence level
Documentation only. No code changed.
Limitations
Headless Chrome anti-aliases a canvas clip slightly differently from whatever made the existing marks (1,327 of 262,144 corner pixels). So the corner's alpha was taken from those marks, and the colour from the draw.
Risks
None at runtime.
Compatibility impact
None.
Remaining work
None planned.