<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/apps/web/lib, branch site/shared-preferences</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>Share the theme and the language across every Progmasoft host</title>
<updated>2026-11-17T11:33:32+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T11:33:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=6d78305900851f98e00cc1b688d1237b5e33f857'/>
<id>6d78305900851f98e00cc1b688d1237b5e33f857</id>
<content type='text'>
A theme chosen on progmasoft.com did not hold on account., viget.,
product. or console., and a language choice sometimes did not either:

- The theme lived in localStorage, which each host keeps for itself. It
  is now the cookie progmasoft_theme of .progmasoft.com, as the language
  is (lib/theme.ts): "light" or "dark", a year, SameSite=Lax, Secure over
  HTTPS, readable by the page's scripts. The bootstrap that sets the theme
  before the first paint reads the cookie; a choice an earlier version left
  in localStorage moves into the cookie once. The theme control writes the
  cookie and reads it again when a page is shown or comes back into view,
  so a tab left open follows a choice made on another host.
- The language cookie is shared (Domain=.progmasoft.com), but a cookie of
  the same name that one host kept from before shadowed it: the browser
  sends both, the host's first. The proxy now expires such a host cookie
  (lib/shared-cookies.ts) for the language and the theme alike, so the
  shared choice holds from the next request on.

Tests: unit tests for the cookie, the bootstrap (run in a vm with a fake
document) and the expiry of shadowing cookies (54 in all); layout tests
that choose a theme and a language on progmasoft.com and find them on the
other hosts, move an old localStorage theme, and clear a shadowing
cookie (144 layout tests pass); tsc, eslint and build pass.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A theme chosen on progmasoft.com did not hold on account., viget.,
product. or console., and a language choice sometimes did not either:

- The theme lived in localStorage, which each host keeps for itself. It
  is now the cookie progmasoft_theme of .progmasoft.com, as the language
  is (lib/theme.ts): "light" or "dark", a year, SameSite=Lax, Secure over
  HTTPS, readable by the page's scripts. The bootstrap that sets the theme
  before the first paint reads the cookie; a choice an earlier version left
  in localStorage moves into the cookie once. The theme control writes the
  cookie and reads it again when a page is shown or comes back into view,
  so a tab left open follows a choice made on another host.
- The language cookie is shared (Domain=.progmasoft.com), but a cookie of
  the same name that one host kept from before shadowed it: the browser
  sends both, the host's first. The proxy now expires such a host cookie
  (lib/shared-cookies.ts) for the language and the theme alike, so the
  shared choice holds from the next request on.

Tests: unit tests for the cookie, the bootstrap (run in a vm with a fake
document) and the expiry of shadowing cookies (54 in all); layout tests
that choose a theme and a language on progmasoft.com and find them on the
other hosts, move an old localStorage theme, and clear a shadowing
cookie (144 layout tests pass); tsc, eslint and build pass.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Fit every page to phones and test the layout with Playwright</title>
<updated>2026-11-16T17:28:33+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T17:28:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=537b1f3a4a605b7aa980eec520628ff37648f683'/>
<id>537b1f3a4a605b7aa980eec520628ff37648f683</id>
<content type='text'>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Serve the Catch3 site at catch3.uk</title>
<updated>2026-11-16T13:27:16+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T13:27:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=62faa7158ce51495dcdd09e7858c23faee707cfd'/>
<id>62faa7158ce51495dcdd09e7858c23faee707cfd</id>
<content type='text'>
Catch3 has a domain of its own. Progmaweb answers catch3.uk with the
Catch3 page, its sitemap and its robots entry; catch3.progmasoft.com and
www.catch3.uk send a 308 to it from nginx, so one address serves the
site. catch3.uk has its own certificate (ops/README.md).

The page said Catch3 adds a C++20 library; it is a C++17 library, in
all four languages of the page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Catch3 has a domain of its own. Progmaweb answers catch3.uk with the
Catch3 page, its sitemap and its robots entry; catch3.progmasoft.com and
www.catch3.uk send a 308 to it from nginx, so one address serves the
site. catch3.uk has its own certificate (ops/README.md).

The page said Catch3 adds a C++20 library; it is a C++17 library, in
all four languages of the page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge main into legal/patent-grant-notice</title>
<updated>2026-11-15T16:34:39+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T16:34:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=c0d96223e2240cc61af194737e3e5dc9faa2f1d2'/>
<id>c0d96223e2240cc61af194737e3e5dc9faa2f1d2</id>
<content type='text'>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The README takes main's sentence, which no longer names the former site,
with PATENTS.md; REUSE.toml keeps the CC0-1.0 annotation of the JSON
Schemas and names AGPL-3.0-or-later alone. The Nginx file of
schemastore.progmasoft.com, new on main, gets the same SPDX expression.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Show Catch3 0.4.0 as its latest release</title>
<updated>2026-11-15T12:30:47+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T12:30:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=18bfd1f74b8465987248c207ed39d3c671becaa2'/>
<id>18bfd1f74b8465987248c207ed39d3c671becaa2</id>
<content type='text'>
Catch3 0.4.0 was released on 2026-11-15 (tag catch3-0.4.0). The catalog of
product.progmasoft.com lists it under Catch3 and on its releases page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Catch3 0.4.0 was released on 2026-11-15 (tag catch3-0.4.0). The catalog of
product.progmasoft.com lists it under Catch3 and on its releases page.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove what is left of the former language and its site (#70)</title>
<updated>2026-11-15T10:53:35+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T10:53:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=1a73486c0f67ddf3bfe3fd01e2258648f81fbb48'/>
<id>1a73486c0f67ddf3bfe3fd01e2258648f81fbb48</id>
<content type='text'>
The dashboard, proxy, documents, issue templates and ops files no longer point at the former language, its site or its repositories. viget.progmasoft.com/api/v1/status answers from the Progmaweb API (5085); the archived website repository is no longer mirrored.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The dashboard, proxy, documents, issue templates and ops files no longer point at the former language, its site or its repositories. viget.progmasoft.com/api/v1/status answers from the Progmaweb API (5085); the archived website repository is no longer mirrored.</pre>
</div>
</content>
</entry>
<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>Merge branch 'main' into feature/product-catalog-like-apache</title>
<updated>2026-11-14T13:45:45+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-14T13:45:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=189d3c6d4fe99dc9c11bd4d45ef40ddc8b29e799'/>
<id>189d3c6d4fe99dc9c11bd4d45ef40ddc8b29e799</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Point product.progmasoft.com/robots.txt at its sitemap; drop unused text</title>
<updated>2026-11-14T13:44:19+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-14T13:44:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=800d828080426f781d374920c5623883844f80ca'/>
<id>800d828080426f781d374920c5623883844f80ca</id>
<content type='text'>
Review of this pull request:

- robots.txt on product.progmasoft.com named the apex sitemap; it names
  https://product.progmasoft.com/sitemap.xml now, as viget names its own.
- details and facts.links were translated in four languages but shown
  nowhere; they are gone.
- Stylelint (Codacy): one header comment block in catalog.css, no type
  qualifier on [aria-current], range notation in its media queries.

Codacy's "object injection" findings are left: every index is a key of a
typed, closed list (ProductSlug, categories, statuses), never input.
Playwright on a production build again: 56 page, language and width
combinations without overflow, console errors or CSP violations.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Review of this pull request:

- robots.txt on product.progmasoft.com named the apex sitemap; it names
  https://product.progmasoft.com/sitemap.xml now, as viget names its own.
- details and facts.links were translated in four languages but shown
  nowhere; they are gone.
- Stylelint (Codacy): one header comment block in catalog.css, no type
  qualifier on [aria-current], range notation in its media queries.

Codacy's "object injection" findings are left: every index is a key of a
typed, closed list (ProductSlug, categories, statuses), never input.
Playwright on a production build again: 56 page, language and width
combinations without overflow, console errors or CSP violations.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Describe Progmasoft without programming languages and compilers</title>
<updated>2026-11-14T13:33:47+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-14T13:33:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=638d81dc4d0cfe554ea952cae2f59ac70534976d'/>
<id>638d81dc4d0cfe554ea952cae2f59ac70534976d</id>
<content type='text'>
The footer of every page, the site description and the home page still
said that Progmasoft builds programming-language infrastructure,
languages and compilers. Since Tala and its tools are archived, they
describe what Progmasoft makes now, in all four languages:

- Footer: "Developer tools and data infrastructure built with durable
  contracts."
- Site and home description: build systems, testing tools, an agentic
  IDE and data infrastructure.
- Home hero: build systems, testing tools, agentic development
  environments, data infrastructure and the services around them.
- The area "Languages and compilers" becomes "Data infrastructure"
  (columnar in-memory formats and engines for large data on the JVM);
  "Developer tools" drops language servers for agentic development
  environments.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The footer of every page, the site description and the home page still
said that Progmasoft builds programming-language infrastructure,
languages and compilers. Since Tala and its tools are archived, they
describe what Progmasoft makes now, in all four languages:

- Footer: "Developer tools and data infrastructure built with durable
  contracts."
- Site and home description: build systems, testing tools, an agentic
  IDE and data infrastructure.
- Home hero: build systems, testing tools, agentic development
  environments, data infrastructure and the services around them.
- The area "Languages and compilers" becomes "Data infrastructure"
  (columnar in-memory formats and engines for large data on the JVM);
  "Developer tools" drops language servers for agentic development
  environments.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
</feed>
