clawdie/clawdie-iso
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: normalize prose dates to DD.mon.YYYY (AGENTS.md rule)

Browse source 
Convert US/ISO prose dates to EU format across iso docs (CHANGELOG, plans,
handoffs, wiki-linked docs). Left as-is (data, not prose): the sample log lines
in FIRSTBOOT.md and the ADMIN-PANEL.md UI mockup (timestamps/snapshot names);
ISO is correct for machine output.

Markdown format gate clean.
This commit is contained in:
Sam & Claude 2026-06-24 16:44:37 +02:00
parent ae36b9f896
commit 61683eeb42
12 changed files with 24 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CHANGELOG.md
View file

@ -52,7 +52,7 @@ _Nothing yet._
--- ---
## [0.10.0] — 2026-06-15 ## [0.10.0] — 15.jun.2026
**Codename:** Operator Image **Codename:** Operator Image
@ -80,7 +80,7 @@ image is meant to work out of the box. Work continues from here toward `1.0.0`.
--- ---
## [0.9.0] — 2026-04-06 ## [0.9.0] — 06.apr.2026
**Codename:** Unified Architecture **Codename:** Unified Architecture

8
PLAN-OPERATOR-USB-NEXT.md
View file

@ -1,7 +1,7 @@
# Plan: Operator USB — Next Round # Plan: Operator USB — Next Round
**Audience:** Codex (FreeBSD agent), Claude (Linux agent), Operator (Sam) **Audience:** Codex (FreeBSD agent), Claude (Linux agent), Operator (Sam)
**Author:** Claude (Linux agent) — 2026-05-20 **Author:** Claude (Linux agent) — 20.may.2026
--- ---
@ -650,7 +650,7 @@ Real-hardware acceptance should be recorded against `doc/AMD-ASUS-XFCE-LIVE-USB-
## 2.2. Live Self-Debug Code Checkout Seed ## 2.2. Live Self-Debug Code Checkout Seed
**Operator request — 2026-06-01 AMD live session:** the next rebuilt operator **Operator request — 01.jun.2026 AMD live session:** the next rebuilt operator
USB should prepopulate the live `clawdie` home with the relevant source trees so USB should prepopulate the live `clawdie` home with the relevant source trees so
the operator can start a local `pi` session from XFCE, log in with a provider, the operator can start a local `pi` session from XFCE, log in with a provider,
and let that agent inspect the live system and the shipped source side by side. and let that agent inspect the live system and the shipped source side by side.
@ -744,7 +744,7 @@ flashing or real hardware proof, leave a brief note in `doc/` (matching existing
handoff convention) with the exact build + verify commands Codex ISO Builder handoff convention) with the exact build + verify commands Codex ISO Builder
should run. should run.
### Claude confirms (2026-05-20) ### Claude confirms (20.may.2026)
Received `bd94b87` ("Clarify operator USB agent roles"). Confirmed Received `bd94b87` ("Clarify operator USB agent roles"). Confirmed
understanding of the 4-role split and git coordination rules. Expanding my understanding of the 4-role split and git coordination rules. Expanding my
@ -769,7 +769,7 @@ and discussed first.
> "Codex ISO developer". That role was later renamed to **Pi ISO Developer** > "Codex ISO developer". That role was later renamed to **Pi ISO Developer**
> (see `AGENTS.md`). Text preserved verbatim as a historical record. > (see `AGENTS.md`). Text preserved verbatim as a historical record.
### Codex ISO developer confirms (2026-05-20) ### Codex ISO developer confirms (20.may.2026)
Received `bd94b87` ("Clarify operator USB agent roles"). Confirmed Received `bd94b87` ("Clarify operator USB agent roles"). Confirmed
understanding of the 4-role split and git coordination rules. understanding of the 4-role split and git coordination rules.

2
doc/AMD-ASUS-XFCE-LIVE-USB-FINDINGS.md
View file

@ -926,7 +926,7 @@ xrandr --query
xfconf-query -c xfce4-panel -p /panels/panel-1 -lv xfconf-query -c xfce4-panel -p /panels/panel-1 -lv
``` ```
## Follow-up live XFCE command evidence — 2026-06-01 ## Follow-up live XFCE command evidence — 01.jun.2026
After the report archive was collected, the operator ran direct `xfconf-query` After the report archive was collected, the operator ran direct `xfconf-query`
checks in the live XFCE session before rebooting. checks in the live XFCE session before rebooting.

6
doc/DEEPSEEK-V4-SMOKE.md
View file

@ -2,7 +2,7 @@
**Status:** PASS — lane confirmed working **Status:** PASS — lane confirmed working
**Owner:** Opencode / Z.ai Integrator **Owner:** Opencode / Z.ai Integrator
**Date:** 2026-05-24 **Date:** 24.may.2026
## Official API Reference ## Official API Reference
@ -19,7 +19,7 @@
| deepseek-v4-flash | deepseek-v4-flash | 1M | 384K | yes | no | | deepseek-v4-flash | deepseek-v4-flash | 1M | 384K | yes | no |
| deepseek-v4-pro | deepseek-v4-pro | 1M | 384K | yes | no | | deepseek-v4-pro | deepseek-v4-pro | 1M | 384K | yes | no |
Deprecated names (retired 2026-07-24): `deepseek-chat` → v4-flash Deprecated names (retired 24.jul.2026): `deepseek-chat` → v4-flash
non-thinking, `deepseek-reasoner` → v4-flash thinking. non-thinking, `deepseek-reasoner` → v4-flash thinking.
### Pricing (per 1M tokens) ### Pricing (per 1M tokens)
@ -29,7 +29,7 @@ non-thinking, `deepseek-reasoner` → v4-flash thinking.
| deepseek-v4-flash | $0.0028 | $0.14 | $0.28 | | deepseek-v4-flash | $0.0028 | $0.14 | $0.28 |
| deepseek-v4-pro | $0.003625\* | $0.435\* | $0.87\* | | deepseek-v4-pro | $0.003625\* | $0.435\* | $0.87\* |
\* 75% promotional discount ends 2026-05-31, then 1/4 of original. \* 75% promotional discount ends 31.may.2026, then 1/4 of original.
## Key Management ## Key Management

8
doc/XFCE-PANEL-BUGS-HANDOFF.md
View file

@ -4,7 +4,7 @@
**Date:** 24.maj.2026 **Date:** 24.maj.2026
**Status:** Visual-polish lane COMPLETE (Pass 1 + Pass 2, on `main`, build-ready: panel XML valid, `build.sh` install paths + Whisker icon verified). → **Awaiting ISO rebuild on the FreeBSD build host (osa) + a boot on the AMD/ASUS box** to check the verification items below. No domedog/config work remains. **Status:** Visual-polish lane COMPLETE (Pass 1 + Pass 2, on `main`, build-ready: panel XML valid, `build.sh` install paths + Whisker icon verified). → **Awaiting ISO rebuild on the FreeBSD build host (osa) + a boot on the AMD/ASUS box** to check the verification items below. No domedog/config work remains.
## Pre-build changes applied (2026-05-24) ## Pre-build changes applied (24.may.2026)
The XFCE Tweaker applied the low-risk config fixes directly to the panel-skel The XFCE Tweaker applied the low-risk config fixes directly to the panel-skel
so the next image carries them. The base AMD ASUS hardware collection has since been recorded in `doc/AMD-ASUS-XFCE-LIVE-USB-FINDINGS.md`. This handoff now tracks only the remaining XFCE panel/icon polish. What changed: so the next image carries them. The base AMD ASUS hardware collection has since been recorded in `doc/AMD-ASUS-XFCE-LIVE-USB-FINDINGS.md`. This handoff now tracks only the remaining XFCE panel/icon polish. What changed:
@ -30,7 +30,7 @@ gradient + triangle motif); the old `clawdie-dark-grad.svg` was removed. Both
assets ship as PNG to avoid depending on a librsvg gdk-pixbuf loader that is not assets ship as PNG to avoid depending on a librsvg gdk-pixbuf loader that is not
in the package lists. in the package lists.
## Pre-build changes applied (2026-05-25) — Pass 2 ## Pre-build changes applied (25.may.2026) — Pass 2
Follow-up operator polish, **config-only** (no build.sh / hardware changes). Follow-up operator polish, **config-only** (no build.sh / hardware changes).
Targets the residual "panel size" + "network/mixer icons too small / Targets the residual "panel size" + "network/mixer icons too small /
@ -66,7 +66,7 @@ FreeBSD/operator side. Pass 2 only improves _proportion and uniformity_.
- [ ] `square-icons` took effect on the systray (network/mixer icons square and - [ ] `square-icons` took effect on the systray (network/mixer icons square and
uniform) — confirm the installed `systray` plugin honors the property. uniform) — confirm the installed `systray` plugin honors the property.
## Pre-build changes applied (2026-06-01) — Pass 3 ## Pre-build changes applied (01.jun.2026) — Pass 3
Follow-up from the AMD live report and direct `xfconf-query` checks: Follow-up from the AMD live report and direct `xfconf-query` checks:
@ -315,7 +315,7 @@ above with findings._
## Config-Change Candidates ## Config-Change Candidates
These are the XML changes that address issues 1, 2, 4, 5, 6. These are the XML changes that address issues 1, 2, 4, 5, 6.
**Applied to the panel-skel on 2026-05-24** (see "Pre-build changes applied" **Applied to the panel-skel on 24.may.2026** (see "Pre-build changes applied"
above). Retained here as the record of what changed and the fallback options if above). Retained here as the record of what changed and the fallback options if
build-host verification shows a fix did not take. build-host verification shows a fix did not take.

2
docs/BUILDER-INSTRUCTIONS.md
View file

@ -1,4 +1,4 @@
# ISO Builder Instructions — Live USB Desktop Layout (2026-06-04) # ISO Builder Instructions — Live USB Desktop Layout (04.jun.2026)
## Overview ## Overview

4
docs/DOME-GEOMETRY-CAPABILITY.md
View file

@ -1,6 +1,6 @@
# Blender vs geodesic-dome-mcp — Capability Comparison # Blender vs geodesic-dome-mcp — Capability Comparison
2026-06-23 | OSA (mother node) | FreeBSD 15.0 23.jun.2026 | OSA (mother node) | FreeBSD 15.0
## The problem ## The problem
@ -50,7 +50,7 @@ marks nodes that can run `geodesic-dome-mcp` (all of them — numpy + Pillow
are universal). Nodes that have Blender installed get an additional are universal). Nodes that have Blender installed get an additional
`has_blender: true` capability for 3D rendering workloads. `has_blender: true` capability for 3D rendering workloads.
## OSA as example (registered 2026-06-23) ## OSA as example (registered 23.jun.2026)
```json ```json
{ {

2
docs/GIS-INTEGRATION-PLAN.md
View file

@ -1,6 +1,6 @@
# GIS Integration — Step-by-Step Implementation Plan # GIS Integration — Step-by-Step Implementation Plan
2026-06-23 | Specification phase | No code yet 23.jun.2026 | Specification phase | No code yet
## Overview ## Overview

2
docs/ONBOARDING-SIMPLIFICATION.md
View file

@ -1,6 +1,6 @@
# Onboarding Simplification — Decision Doc # Onboarding Simplification — Decision Doc
2026-06-22 | colibri#143 (zot-rpc-driver) | clawdie-iso 22.jun.2026 | colibri#143 (zot-rpc-driver) | clawdie-iso
## Context ## Context

6
docs/SECURITY-BASELINE.md
View file

@ -1,9 +1,9 @@
# Security Baseline — Live USB Boot Checklist # Security Baseline — Live USB Boot Checklist
2026-06-23 | OSA audit → live USB alignment 23.jun.2026 | OSA audit → live USB alignment
Cross-reference of security checks that should pass on every booted Cross-reference of security checks that should pass on every booted
Clawdie USB. Derived from the OSA security audit on 2026-06-23. Clawdie USB. Derived from the OSA security audit on 23.jun.2026.
## Boot-time checks ## Boot-time checks
@ -78,7 +78,7 @@ Clawdie USB. Derived from the OSA security audit on 2026-06-23.
These exceptions should NOT be present on a booted USB — the USB is a These exceptions should NOT be present on a booted USB — the USB is a
single-user operator station, not a public server. single-user operator station, not a public server.
## Tests performed on OSA (2026-06-23) ## Tests performed on OSA (23.jun.2026)
- ✅ SSH MCP from colibri user: `ssh -i mother-mcp colibri@localhost 'tools'` — works - ✅ SSH MCP from colibri user: `ssh -i mother-mcp colibri@localhost 'tools'` — works
- ✅ Home dir ownership fixed: `chown colibri:colibri /var/db/colibri` - ✅ Home dir ownership fixed: `chown colibri:colibri /var/db/colibri`

2
docs/SETUP-USB-TO-MOTHER.md
View file

@ -1,6 +1,6 @@
# Setup: USB → Mother MCP Connection # Setup: USB → Mother MCP Connection
2026-06-23 | Step-by-step | Tested on OSA + 0.11 USB 23.jun.2026 | Step-by-step | Tested on OSA + 0.11 USB
Connects a booted Clawdie USB to the mother node (OSA) via MCP over SSH. Connects a booted Clawdie USB to the mother node (OSA) via MCP over SSH.
After setup, `clawdie-hw-probe` runs on the USB, the hardware profile is After setup, `clawdie-hw-probe` runs on the USB, the hardware profile is

2
docs/USB-MOTHER-MCP-CONNECTION.md
View file

@ -1,6 +1,6 @@
# USB → Mother MCP Connection Plan # USB → Mother MCP Connection Plan
2026-06-23 | Implementation plan | No code yet 23.jun.2026 | Implementation plan | No code yet
## Goal ## Goal