Repository navigation
Documentation current at 1.2.1: prose, comments, six new documents, proposal records (DR-184) - #36
Merged
Merged
Conversation
Documentation only, from the delta sheet contract-1.2.1-delta.md: prose, header comments and two schema description strings. No schema keyword other than description changes and no code behaviour changes. - README.md: /1.2.1/ frozen copy; the 1.1.0 release candidate (e91afb0) is what could not run its own test; the npm test comment names everything the run checks; lease rules name L3 and the rules(lease, context) hook; the development-stability fields at 1.2.1 - CHANGELOG.md: 1.2.1 intro (schema set stays 1.2, schemaSetVersion follows the package); 110 entries cover 115 tightenings; tool_args stability wording; 664 properties at 1.2.0 annotated with 666 at 1.2.1; RE2 job history; pages.yml dispatch note; ten words; the duplicate Added and Fixed headings inside [1.1.0] merged; the 1.1.0 candidate named - SPEC-agent-lease-manifest.md: section 9 names schema set 1.2 (any 1.x under section 10) and rules L1 to L3 with the journal condition; an editorial row in section 13 - conformance/traceability.json: clauses 9-1 and 9-3 re-affirmed - CONTRIBUTING.md: what npm test checks; which findings need which lock format; how a definition-path allow-list entry covers referring properties within its schema - GOVERNANCE.md: release step 4, release.yml dispatches pages.yml on main - SECURITY.md: lease-record in the lease-escape scope - schemas/audit-event.schema.json, schemas/cdi-signal.schema.json: "ten words" in the details propertyNames description; conformance/suite/draft7/{audit-event,cdi-signal}.json regenerated by npm run lock - .github/workflows/contract.yml, release.yml: comment and warning text - conformance/runner.mjs, ids.mjs, schema-checks.mjs, check-additive.mjs, generate-schemas-lock.mjs, generate-contract-types.mjs: header comments and the generated-header string Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
…conformance report (DR-184, task 2.2) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
…he pin (DR-184, task 2.3) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jason Cruz Falzon <jason@cognitivedelivery.co.uk>
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
1 participant
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.
Documentation only. No schema keyword other than two
descriptionstrings changes; the additive guard reports zero findings againstmain; no release is needed.Why. A read-only audit on 6 October found the contract's own gates current at the tag and the prose around them not: the 1.1.0 self-test defect attributed to the published tarball (true only of the pre-tag candidate), "eleven words" over a list of ten,
x-stabilitywhere the shipped marker is a$comment, SPEC §9 at "schema set 1.0" without rule L3, CONTRIBUTING describing four checks where there are a dozen, header comments naming the wrong findings and the wrong counts.What. Three signed commits, one per spec task:
docs/implementing.md(with a worked example executed from the installed package),docs/upgrading-1.0-to-1.2.md,docs/decisions.md,docs/conformance/cdf-harness.md, five proposal records (four accepted, host ports rejected for 1.x citing DR-183 D2), README Layout and links.[Unreleased]entry and the README evidence figures at the pin.Checks.
npm testConformant (Layout names every entry; traceability 87 mapped);node check-additive.mjs --baseline-ref mainadditive, 0 findings;tooling/changelog-section.mjs 1.1.0exit 0; the harness's documentation-currency gate reports zero stale lines under this repository.Governed as harness spec
update-every-document-describes-governance(DR-184); Linear COGDEV-269.🤖 Generated with Claude Code