progmaweb/docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md, branch docs/code-of-conduct The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API. Name the copyright license alone in SPDX expressions 2026-11-15T10:14:38+00:00 Leitwolf11 2026-11-15T10:14:38+00:00 3bda6d7bc28c5aa588418d12d9e3129f8526df50 The Progmasoft Patent Grant is a separate permission added to the copyright license, not an exception to it, so joining the two with WITH said something the grant does not do. What makes the grant apply is the PATENTS notice of the repository (Section 9 of the grant), not the SPDX expression of each file. Every project-owned file now carries SPDX-License-Identifier: AGPL-3.0-or-later, and package.json says the same. PATENTS becomes PATENTS.md: project-owned software in the repository is covered by the Patent Grant, Version 1.1, whose canonical text is unchanged under LICENSES/; third-party material keeps its own terms. NOTICE.txt and the README point to PATENTS.md. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1 
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Document the ViGet API in full and take zod 4.6.7 for eslint 2026-10-29T09:42:13+00:00 Leitwolf11 2026-10-29T09:42:13+00:00 285e1024da64234b30b0fa425ffd6bf348119db4 The documentation check of the backend found the private members of ViGet/ without a summary and no page for its namespace: - Summaries for every field and helper method of the catalog, the descriptor, the properties reader, publishing and the endpoints. - docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md describes the namespace. - The two regular expressions of TazelPluginDescriptor are excluded from the reference like AccountNamePolicy.CanonicalPattern: the generator replaces their comment with its own. The dependency audit found GHSA for zod < 4.6.6, which can exhaust memory while validating oversized constrained collections. Only eslint-plugin-react-hooks reaches it, and it accepts any zod 4, so an override takes 4.6.7 until the plugin resolves a fixed release itself. pnpm audit --audit-level high finds nothing. 
The documentation check of the backend found the private members of
ViGet/ without a summary and no page for its namespace:
- Summaries for every field and helper method of the catalog, the
  descriptor, the properties reader, publishing and the endpoints.
- docs/api/namespaces/Progmasoft.Progmaweb.Api.ViGet.md describes the
  namespace.
- The two regular expressions of TazelPluginDescriptor are excluded from the
  reference like AccountNamePolicy.CanonicalPattern: the generator replaces
  their comment with its own.

The dependency audit found GHSA for zod < 4.6.6, which can exhaust memory
while validating oversized constrained collections. Only
eslint-plugin-react-hooks reaches it, and it accepts any zod 4, so an
override takes 4.6.7 until the plugin resolves a fixed release itself.
pnpm audit --audit-level high finds nothing.