CI 2589 step `format` failed on exactly one file: this one, the plan document I hand-wrote. prettier --check reproduces locally, rc=1, same single file. That is worth stating for the review: the other 103 stamped documents pass `prettier --check` unchanged, so the `---\nkind:\nstatus:\n---` front matter block is already prettier-clean. The formatting failure was in my prose, not in the contract header. Diff is 31 lines in, 31 out, all table column padding. No content change.
This commit is contained in:
@@ -20,7 +20,7 @@ files. The flatten plan says 130; the arithmetic does not close (318 total = 134
|
|||||||
## Applied
|
## Applied
|
||||||
|
|
||||||
| bucket | count | note |
|
| bucket | count | note |
|
||||||
| --- | --- | --- |
|
| --------------------------------- | ----- | ----------------------------------------- |
|
||||||
| stamped `kind` + `status: active` | 103 | this pass |
|
| stamped `kind` + `status: active` | 103 | this pass |
|
||||||
| held, operator judgement | 19 | section "Needs a decision" below |
|
| held, operator judgement | 19 | section "Needs a decision" below |
|
||||||
| held, cites the moving path | 3 | the three `SUPERSEDED` TASKS.md stamps |
|
| held, cites the moving path | 3 | the three `SUPERSEDED` TASKS.md stamps |
|
||||||
@@ -85,7 +85,7 @@ classifying.
|
|||||||
Fill the `kind` column with a value from the contract, or `superseded-by: <path>`.
|
Fill the `kind` column with a value from the contract, or `superseded-by: <path>`.
|
||||||
|
|
||||||
| path | proposed | why it is not mechanical |
|
| path | proposed | why it is not mechanical |
|
||||||
| --- | --- | --- |
|
| --------------------------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||||
| `docs/README.md` | `guide` | It also **prescribes** the competing front-matter convention (see below). Whatever kind it gets, its body needs an edit. |
|
| `docs/README.md` | `guide` | It also **prescribes** the competing front-matter convention (see below). Whatever kind it gets, its body needs an edit. |
|
||||||
| `docs/SITEMAP.md` | `guide` or `projection` | If it is generated from the tree it is a projection and needs a drift test. If hand-maintained it is a guide that goes stale silently. Nobody has said which. |
|
| `docs/SITEMAP.md` | `guide` or `projection` | If it is generated from the tree it is a projection and needs a drift test. If hand-maintained it is a guide that goes stale silently. Nobody has said which. |
|
||||||
| `docs/federation/SETUP.md` | `guide` | Reads as a guide. Federation tier status is the open part: if the tier is shelved this is `superseded`. |
|
| `docs/federation/SETUP.md` | `guide` | Reads as a guide. Federation tier status is the open part: if the tier is shelved this is `superseded`. |
|
||||||
|
|||||||
Reference in New Issue
Block a user