<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/docs/api/toc.yml, branch site/phone-layout</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Name the copyright license alone in SPDX expressions</title>
<updated>2026-11-15T10:14:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T10:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=3bda6d7bc28c5aa588418d12d9e3129f8526df50'/>
<id>3bda6d7bc28c5aa588418d12d9e3129f8526df50</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Add a DocFX documentation gate for the API</title>
<updated>2026-10-03T10:04:35+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-03T10:04:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=ca41877fafbac6cffc3e78db1d3306112e8acc60'/>
<id>ca41877fafbac6cffc3e78db1d3306112e8acc60</id>
<content type='text'>
The backend workflow now builds the API reference with DocFX and treats
every warning as an error, so an unresolved reference or a broken link
fails the check.

- docs/api holds the DocFX project: it reads apps/api/Progmaweb.Api.csproj
  and includes internal members, because the service is an application and
  most of its types are internal.
- .config/dotnet-tools.json pins docfx 2.81.0, so CI and a local run use the
  same version through `dotnet tool restore`.
- The workflow also runs when the DocFX project or the tool manifest change.
- `just api-docs` runs the same two commands locally.
- The generated site and metadata are ignored.

The gate does not require documentation comments: the API has none yet, and
DocFX does not report an undocumented member. Requiring them is a separate
change to the C# sources.

Verified locally with docfx 2.81.0 on the .NET 10 SDK: the build passes with
no warnings, and a broken link in the overview page makes it fail.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The backend workflow now builds the API reference with DocFX and treats
every warning as an error, so an unresolved reference or a broken link
fails the check.

- docs/api holds the DocFX project: it reads apps/api/Progmaweb.Api.csproj
  and includes internal members, because the service is an application and
  most of its types are internal.
- .config/dotnet-tools.json pins docfx 2.81.0, so CI and a local run use the
  same version through `dotnet tool restore`.
- The workflow also runs when the DocFX project or the tool manifest change.
- `just api-docs` runs the same two commands locally.
- The generated site and metadata are ignored.

The gate does not require documentation comments: the API has none yet, and
DocFX does not report an undocumented member. Requiring them is a separate
change to the C# sources.

Verified locally with docfx 2.81.0 on the .NET 10 SDK: the build passes with
no warnings, and a broken link in the overview page makes it fail.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
