wiki: refresh Module-Catalog + Analyzers + Home + sidebar + FAQ + Getting-Started
10 days of ecosystem growth had drifted the wiki out of sync.
## Module-Catalog
- Bump satellite count framing from 40+ to 50+ (current actual via
nuget profile listing)
- Bump Tamp.Core version refs from 1.6.0 to 1.11.1 throughout
- New section: Classic Windows deploy chain (Wave 4) — SqlPackage,
SqlCmd, MSBuildClassic, MsDeploy
- Expanded supply-chain security section: split into Contract
packages (Sarif, Sbom), SBOM producers (CycloneDx.V6, Syft),
scanners (TruffleHog/CodeQL/OpenGrep/OsvScanner/Trivy/Grype/
SonarScanner/Eslint), triage sinks (DependencyTrack.V1,
DefectDojo.V2), and the one-import Security.Pipeline meta
- New section: Notifications — Tamp.Telegram (with Slack/Discord
siblings flagged as planned)
- New section: Telemetry/observability backend — tamp-beacon
self-host server
- New section: Editor integration — Tamp for VS Code (vsix sideload
from GitHub Releases; Marketplace deferred)
- Add Tamp.Eslint.V9 to JS/TS toolchain section
- Add Tamp.GitHubAttest to source-control section
- Add Tamp.AdjacentContainer.Local to containers section
- Replace stale Tamp.OpenGrep.V1 / Tamp.Syft.V1 references with the
renamed Tamp.OpenGrep / Tamp.Syft (per the 1.11.1 reconcile);
added an explicit 'Naming reconcile' subsection explaining the
rename and that old packages remain on nuget at 1.11.0
- Add Tamp.Eslint.V9 + Tamp.MSBuildClassic to the naming convention
examples
- New Common stack: 'Hybrid / modernized .NET on-prem deploy' using
MSBuildClassic + SqlPackage + SqlCmd + MsDeploy
## Tamp-Analyzers
- Bump header range from TAMP001-TAMP004 to TAMP001-TAMP006
- New TAMP005 section (FromPath field shadowing; <Tool>Bin
convention)
- New TAMP006 section (Target property shadowing)
- New section: Reflection-bound field warning suppressor
(CS0649 false-positive suppression for [Parameter] / [Secret]
/ [Solution] / etc. fields)
## Home
- 40+ → 50+ satellite count
- Analyzer range TAMP001-TAMP004 → TAMP001-TAMP006
- Add Tamp.Eslint.V9 to JS toolchain inline list
- Add Classic Windows deploy chain (Wave 4) bullet
- Expand Supply-chain security bullet to cover the full Wave 1+2+3
chain (foundation contracts, producers, scanners, sinks, meta)
- New Notifications bullet (Tamp.Telegram)
- New Editor integration section pointing at tamp-build/tamp-vscode
+ flagging the planned Fleet sibling
- Add ADR-0018 diagnostics emission contract bullet to Execution and
observability section
- Add Tamp.Sarif, Tamp.Sbom, Tamp.Templates.AspNet to Foundation
- Add Tamp.GitHubAttest to source-control
## _Sidebar
- 'Module Catalog (canonical list, 50+ satellites)'
- TAMP001-TAMP004 → TAMP001-TAMP006
- New 'Editor integration' nav section pointing at tamp-vscode
## FAQ
- Pre-1.0 framing was stale (Tamp.Core 1.x has been GA since
2026-05-10) → updated to reflect prod-ready posture with the
dogfood-Release-pipeline supporting evidence
- '40+ satellites' → '50+'
- Tamp.Core version refs in min-version examples: 1.6.0 → 1.11.1
## Getting-Started
- Resolved contradiction between 'Templates (0.2.0+)' section
(listing minimal/library/monorepo) and 'Template selection
(preview)' section (claiming only minimal ships). All three
templates DO ship today per Tamp.Cli source — removed the stale
'preview' caveat and replaced with a 'Template availability'
section clarifying embedded vs NuGet-distributed template
resolution.
docs(wiki): clarify satellite-to-Tamp.Core version semantics
Add a "How satellites depend on Tamp.Core" section to Module-Catalog.md
explaining:
- NuGet PackageReference Version="1.6.0" is min-version (>= 1.6.0), not
a pin — the satellite-sweep-per-Core-bump pattern we were doing was
unnecessary except when needing new Core API or IVT (the latter retired
in 1.6.0 via TAMP004).
- Decision table: when does a satellite actually need to bump its Core
minimum? (Patch/minor: no. Wants new API: yes. New analyzer trip: yes.
Major: yes.)
- Why this matters for the recent onboarding wave's velocity.
- NuGet range-syntax reference table — npm-style ranges supported, but
first-party satellites stay on bare 1.6.0 form since tighter pinning
is an adopter choice.
Add corresponding FAQ entry: "When Tamp.Core ships a new minor, do all
40+ satellites need to re-publish?" with the short answer and a link
to the Module Catalog section.
Both are documentation of existing semantics — no satellite changes
needed.
Wiki content: build authoring, modules, primitives, CI hosts, migration, FAQ, glossary