tom_specs_core 0.4.0

Core annotations and shared types for TomSpecs document model families.

Changelog

0.4.0

• Field.multiple: a reference field that holds several ids, written comma-separated. Without it a reference field holds one id, and the instance tier reports a list there as multipleReferences.

0.3.1

• Documentation only: CodeSpecPart.backgroundJob names the interval trigger beside cron, calendar and event.

0.3.0

• Field.productOf: a value stated as the product of other fields (numbers, or an enum's 1-based position), checked by the instance tier (derivedValueMismatch).
• Field.rankOf: a value stated as a rank by another field of the same form, highest first, checked over every instance of the form.
• Field.countOf targets may start with ./ to count only the entries beneath the section holding the form.

0.2.3

• Field.code: a form field whose value is code, not prose — a regular expression, a CHECK expression, a formula. The markdown rendition writes it as an inline code span and the import unwraps it, so ]( in a regex stays literal instead of becoming a link.

0.2.2

• Field.countOf: a form field stating a count of entries the document holds names them (<SECTIONID> or <SECTIONID>.<formField>=<value>, summed), so the instance tier can hold the stated number to the lists (countMismatch).

0.2.1

• Documentation only. The README and doc/ pages link to the CodeSpecs mapping and derivation contract at their new home in tom_core_codespecs, so the links resolve for a reader of the published package.

0.2.0

The annotation catalogue grew with the model it annotates: 43 files, +2400 lines since 0.1.0.

• New annotations. @CodeSpecKind / CodeSpecPart (the type-level DocSpecs↔CodeSpecs routing), @FollowUpKind / FollowUpProcess, @NoArtifact / NoArtifactReason — the three routing verdicts that make the ROUTE-TOTAL structural invariant checkable — plus @CodeSpecsProjection, @AccessKey, @AllowedTags, @Case/@CaseOf, @ValidationPrompt and the refersTo target on Field, which turns a free-text id contract from hint prose into something both validation tiers can enforce.
• DocSpecsSection gains codeSpec, the concrete forward link from a section to the CodeSpecs code it was realised as.
• The package is documented: doc/annotations.md, doc/sections.md and doc/index.md, with the README as the annotation catalogue itself.
• No behaviour to break — these are annotations — but the catalogue is larger, so a consumer pinned to 0.1.0 sees none of it.

0.1.0

Initial development release (pub.dev 0.x channel, BSD-3-Clause).

• csra8: CodeSpecPart.reporting (CE-RP) is active, not deferred. Its doc comment now carries the live mapping — the grouped projection built on TomReportDefinition / TomReportResult (tom_core_codespecs) over the tom_core_server query and rendering substrate, marked by @CsReport, @CsReportColumn, @CsReportChart and @CsReportParameter — and records why CE-RP is not a composition of serverApi + dataAccess + form. The enum is unchanged at 28 values; only the readiness split moves, to 26 active / 1 deferred (workflow, deferred permanently).

• csm2r8: reserve the 9 deferred CodeSpecs element candidates (codespecs_mapping.md §4.3) in the CodeSpecPart enum — identity, schemaMigration, workflow, notification, backgroundJob, auditLog, featureFlag, fileStorage, reporting. Mapping-only: a SOM section may carry @CodeSpecKind with these now, but each has no Cs* annotation, built-on tom_core class or generated code until promoted into codespecs_mapping.md §4.1. Enum now holds 29 values (20 active + 9 deferred).