Skip to content

ArcKit v6.23.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 02:23
· 47 commits to main since this release

Added

  • A recipe target can set min_lines, the fewest lines its document may have
  • A folder written for the business, an upgrade path for worksheets, unchecked text shown to the signer, and no new version for a fault outside the body
  • A build recipe that writes the drafts and confirms nothing
  • Five commands and the overlay's checklist
  • Four templates whose body is the helper's print, placed whole
  • Register the overlay: manifest, marketplaces, converter and test lists, eight document types
  • A special-process own entry names the pack's process it covers
  • Status, the completion record and sign-off
  • Render, check and reference, the pack's words and the business's confirmed answers
  • Answer worksheets, generated from the data and parsed exactly
  • Render-limits-check.py, the limits table for reading against the PDF
  • Limits.json, the pack's numbers and limits, one entry per place printed
  • Transcribe the completion record and the diary, pages 78 to 100
  • Transcribe the front matter, pages 1 to 10
  • Page objects for the front matter and diary, with form markers
  • Transcribe Management (MG), pages 64 to 77
  • Transcribe Cooking (CK), pages 48 to 63
  • Transcribe Chilling (CH), pages 38 to 47
  • Check-it blocks carry the column headings printed after CHECK IT
  • Column groups for a label printed across several table columns
  • Transcribe Cleaning (CL), pages 27 to 37
  • Transcribe Cross-contamination (XC), pages 11 to 26
  • Note question type, empty-text prompts, per-paragraph reading match
  • Data schema, source record and the helper's loader and validator

Fixed

  • The review's findings on the open-items fixes
  • A reworded profile question still upgrades, the same signer is not recorded twice, and six sentences say what is true
  • The comment in every document says truly what ends a sign-off
  • Limits.json lists the printed mentions the independent read found missing
  • The sign-off summary says what a sign-off covers only at the marked end
  • The sign-off command changes the file only with the Edit tool and leaves the hook's provenance section alone; two graders read the live run truly
  • The readable status says of a slip in a header cell that a sign-off is recorded and the cell is not what a signed document has there
  • Asking to sign a document already signed and marked ends marked and says so; every stop on a document that is not signed off leaves its header reading as unsigned
  • An upgrade knows each question by the pack's own words for it, and refuses lines that are another question's or no question's
  • The sign-off command ends marked or not marked and says which; an entry's title is the person's; nothing of the business leaves its folder
  • An upgrade refuses lines that are far closer to another question's wording, the newest sign-off is not recorded twice, and three messages say what is true
  • Pre-approve reading the plugin's own files, now that the manual rule names the registry
  • Publish config/, and health names the registry by its plugin-root path again
  • The sign-off command shows the header before recording and marks it in one short loop; the check command says when a header is still to be marked
  • The signer is shown rows, comments and a build's topic that nobody checked, the record says so, and a slip in any marked cell is one line
  • A worksheet upgrade is never written unseen, never moves an answer, and lists every line it changes
  • The folder step compares each file whole, so a README someone has added to is left alone
  • A Gemini path the shell must expand inside double quotes starts with $HOME
  • The manual stale-draft rule names the registry without a plugin-root path
  • A type whose status only its own command sets is not called a stale draft
  • The recipe builds the own methods document, each target with a min_lines measured from its smallest document
  • A slip while a sign-off is marked gives one line and cannot end with a header that reads DRAFT
  • A new version only when a signed file is out of step, and the sign-off step shows the newest sign-off exactly
  • A sign-off leaves out of its fingerprint only what the commands and the hook write, and the check reads a header row however it is typed
  • A second header row cannot hide a claim, and a sign-off binds the Revision History but for its approval cells
  • Every document says when a business is out of coverage, a header takes nothing from configuration, and status says what is true
  • The worksheet keeps a written procedure exactly, holds a half-given own entry, and its guidance says only what is true
  • A sign-off covers the document a person reads, and a header cannot claim one nobody recorded
  • A withdrawn answer is asked about then cleared, dates need their year, and the examples follow the real questions
  • The version rule holds inside a build, a change is recorded like a first answer, and the recipe drops its health step
  • The commands record only what the person says, and never write over a signed document
  • Paperclip runs a command's bundled scripts from the package, and the rest from the project
  • The template lookup reads as one path on Codex
  • The regime index lists the eight food safety codes
  • Status says true things about a misplaced worksheet, a failed check and a matching sign-off
  • Only a finished document reads as signed off, and every unfinished line says what to do next
  • A value may hold the joiners, direction marks and soft hyphen that writing needs
  • Check reads headings and markers as a person writes them, and hidden characters are refused
  • Answers are labelled and escaped, and check sees more
  • An adapted method names who decided it
  • CH-01-Q20 asks about all chilling equipment, and four more slips are reported
  • Every worksheet question carries its context, and nothing typed is credited to the wrong place
  • Worksheets pass markdownlint as they stand, and the fixture cafe agrees with itself
  • Worksheets report what they used to drop, and say what each question is about
  • The check sheet explains itself and names the owner's copy of the PDF
  • Limits for the 4-weekly review's cadence and each display rule's "only once"
  • The schema refuses fromImage on any diary page not listed
  • Make validateData as strict as the schema, with a shared fixture and mutation table

Changed

  • The build recipe has been planned in a dry run
  • The limits sheet says why the two stage clean is listed once, and the test repository is listed
  • Two graders judge a run as it reads
  • The refused sign-off test tells a redirect to /tmp from a workspace that lives under /tmp
  • The provenance note says when core's hook stamps a document, not that it stamps every one
  • The shell graders see a table row's sed, a copy or cd to the temporary folder and a relative file at the workspace; both sign-off cases get the two outside-the-project graders
  • The behaviour cases fail a marking that changes another line, a reworded title, a field nobody gave, and anything sent outside the project
  • The provenance note says what Claude Code's documentation says about the overlay's exact pin
  • The README floor check reads "requires", "minimum", "at least" and "or newer" too
  • Markdownlint skips eval recordings under the overlay mirrors too
  • Say truly who set the food documents' status, what the monitor said, and how health and the monitor differ
  • The four new behaviour cases see the likeliest mistakes
  • The guides say what happens with nobody there to agree to an upgrade, and what a person signing is shown
  • The overview says health leaves these documents out of long-running drafts only
  • Say that the food overlay relies on the Build Provenance block's exact form
  • Markdownlint skips eval recordings and the local venv, and git ignores the root uv.lock
  • Run the scripts/tests node checks with the pytest suite
  • Every overlay README states core's Claude Code floor, held by a test
  • List the UK legacy IT overlay wherever the other overlays are listed
  • The own methods cases also fail a hazard or a figure nobody gave
  • The new behaviour cases' worksheets are held to the helper's own layout
  • The check guide says what the command may now change in a worksheet, and the sign-off guide says when marking is finished
  • Two more pairs of behaviour cases, for sign-off and for own methods
  • The guides say what a new folder holds, that it is kept private, and what happens when the overlay's wording changes
  • The guides say truly what a document shows of an unconfirmed answer, and what leaves a sign-off standing
  • With no written procedure yet, what the person has said is still kept
  • A pair of behaviour cases for the Cooking safe methods
  • Guides an owner can start from and rely on
  • Say that only confirmed answers reach the documents
  • The check guide and overview say exactly what the commands do
  • Each command guide names the command in Codex and Copilot
  • README, CLAUDE.md, CONTRIBUTING, RELEASING and the changelog name the overlay
  • The UK food safety overlay on the site, in llms.txt and the dependency matrix
  • Guides for the person running the business
  • Sign off once everything is finished, the profile last, and the Claude Code floor is core's
  • Pin the review's rules, the version rule as code, and the fields the helper requires
  • The README names another tool's command in a form the mirror keeps
  • The README lists the commands, and the changelog names them
  • The commands, templates and checklist, before they exist
  • Move the data-validation tests into uk-food-data.test.mjs
  • Spell the raised zero, en dash and curly quotes in the limits tests as escapes
  • Where the FSA's 38 individual sheets differ from the full pack
  • Compare the whole pack page by page, and the completion record's printed order
  • Guard rails for fromImage, page titles, the diary path and the shared lists
  • Split a text-layer token at any whitespace inside it
  • Read a soft hyphen as a printed hyphen only at the end of a part another part follows
  • Refuse a join with a count below 1, and require a reason on every exception
  • Text-layer fixture, coverage test and reading comparison