You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lint orders findings within a line by where they stand. Several
findings of one kind on one line, such as an open term and a ?, or
two misplaced anchors, came out in an order that depended on the
kind; they now appear from the start of the line to its end.
lint reads no fields of an element of no type. A heading with
an anchor where the layout allows no element is reported once as element-unplaced; a field under it, such as - Contact: ?, no
longer adds an undecided ask.
The model, stated more precisely
The spec tree's Markdown is read as CommonMark 0.31.2 with GitHub's
tables, through the terms heading, table and link and the places
Proviso departs from them: a byte order mark at the start of a file
is ignored, and only headings and tables at the top level of a file
count. Rules and rows now state the corners lint already handled: the
label of a fence is the first word of its info string, ID= is an
anchor, only a - list is fields, \| is a pipe in a cell, the
first table after a rule block is its Examples table, [text]( makes
no term mark, and placeholder names may use letters of either case.
Only a rule block's marks of an open term hold an element back from
being built.
update reads the stamp of a skill or agent installed as a symbolic
link through the link, but never writes through it or replaces it: a
stale linked file is not written, and update exits with 2. version
reads such a stamp as update does. A folder linked on the way to a
skill or agent, such as a shared skills folder, is the engineers'
setup, which the system's design boundary now names.
Documentation
Tests with teeth:
the first mutation run on Proviso itself, its 23 survivors, and how
each was decided.