wiki: reconcile with the 1.13.0 codebase + open up the components gap Verified against the nuget.org package list and the tamp-build org. Module-Catalog: - Tamp.Core "Current: 1.11.1" -> 1.13.0. - Note the 1.12.0 split: the six security wrappers now ship from their own satellite repos on a version line that has diverged from Tamp.Core's. Only Tamp.Sarif / Tamp.Sbom / Tamp.Security.Pipeline remain in the core repo. - Add Tamp.Telemetry and Tamp.Ingest.V1 to the telemetry section, which previously listed only the tamp-beacon server and no NuGet packages. - Add tamp-findings (attestation / federal-readiness evidence dashboard). - New Accessibility section for Tamp.AxeCore. Home: add Tamp.Kubectl, Tamp.AxeCore, Tamp.Telemetry, Tamp.Ingest.V1. Migrating-From-NUKE: the components section said Tamp.Components was "a Tier 3 plan", which reads as scheduled work. It isn't — it is not designed, not built and not scheduled. Say so plainly, tell migrators what to write by hand in the meantime, and invite an ADR from anyone with a real components-shaped build, since they are better placed to design it than the maintainers are.

BrewingCoder committed Jul 13, 2026

Add Paths-And-Filesystem reference page + sidebar entry + NUKE-migration crosslink Canonical reference for the AbsolutePath FS surface (existing + new in Tamp.Core 1.8.0). DasBook canary feedback: adopters scanning READMEs without a dedicated wiki page never built a complete mental model of what AbsolutePath could do, leading to redundant System.IO drops. Covers: construction + components + existence + creation/deletion + read/write + copy/move + hashing + globbing + OS temp-path factories + TampBuild.Scratch lifecycle. Closes the loop on the "Tamp.FileSystem satellite" design question (TAM-202) — answered as "no satellite, native on AbsolutePath". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

BrewingCoder committed May 13, 2026

docs: refresh for 1.2.0 surface — Internal/Default/CleanArtifacts/object-init - Build-Script-Authoring: anatomy uses 1.1.0+ surface (Internal/Default, CleanArtifacts, no .TopLevel(), object-init authoring style); lifecycle table marks TopLevel() obsolete; Default/Ci shortcuts updated. - Module-Catalog: module-shape example shows both fluent and object-init. - Getting-Started: scaffolded Build.cs uses .Default() and drops the obsolete TopLevel() marker. - Glossary: Internal and Default entries replace TopLevel; Wrapper entry notes the 1.2.0 dual-style overloads. - Migrating-From-NUKE: Unlisted → Internal mapping (renamed in 1.1.0+); migration recipe step 7 updated; .TopLevel() noted as obsolete on upgrade. - Tamp-NetCli: Push target example stripped of .TopLevel(). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

BrewingCoder committed May 11, 2026

Wiki content: build authoring, modules, primitives, CI hosts, migration, FAQ, glossary

BrewingCoder committed May 10, 2026