chore: rename Steelbore → Spacecraft Software + test-kernel TSC instrumentation

Rebrands the umbrella organization across docs and code from
"Steelbore" to "Spacecraft Software" and rolls every SFRS / PRD
identifier from the `SB-` prefix to `SS-`. Touches:

- Top-level context docs: AGENTS, CLAUDE, CONTRIBUTING, SKILL,
  TODO, CHANGELOG, and the PRD mirror.
- In-source string references in zamak-cli (json/error/output/meta
  module headers + agent docs_url), zamak-core (gfx palette
  comment + tui menu title), zamak-bios (entry / trampoline
  module headers), zamak-stage1, zamak-theme.

Folds in two adjacent changes that share the same touched files:

- `zamak-test-kernel::main` now emits `KERNEL_ENTRY tsc=<u64>`
  before the existing `ZAMAK` / `LIMINE_PROTOCOL_OK` sentinels
  via a new `rdtsc()` helper. Lets M6-3 Part 2 compute
  bootloader-overhead deltas by capturing the same kernel under
  ZAMAK vs Limine v10.x and subtracting the absolute TSC values.
  Additive output — existing boot-smoke / linux-bzimage sentinel
  asserts are unaffected. CHANGELOG `[Unreleased]` entry added.
- `.gitignore`: `/dist/` (M6-3 Part 2 baseline staging) and
  `tmp.txt`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: UnbreakableMJ

.gitignore

@@ -10,12 +10,16 @@ target/
 *.obj
 *.o
 
+# M6-3 Part 2 baseline staging (local-only, scp'd to test boxes)
+/dist/
+
 # Antigravity/Internal
 .gemini/
 
 # Claude Code session state + exported transcripts
 .claude/
 Chat.txt
+tmp.txt
 2026-*-this-session-is-being-continued-from-a-previous-c.txt
 
 # IDEs

AGENTS.md

@@ -15,7 +15,7 @@ OpenAI Codex CLI, Cursor, Aider, and similar tools.
 - **Type:** Rust bootloader (BIOS + UEFI, x86-64 / AArch64 /
   RISC-V 64 / LoongArch64)
 - **Status:** active development; reference PRD v1.3.0
-- **Organisation:** Steelbore
+- **Organisation:** Spacecraft Software
 - **License:** GPL-3.0-or-later on every source file
 
 ## Coding conventions
@@ -63,7 +63,7 @@ OpenAI Codex CLI, Cursor, Aider, and similar tools.
 ## CLI conformance
 
 Every host CLI binary (`zamak-cli` today, future ones the same)
-must conform to `SB-SFRS-STEELBORE-CLI v1.0.0`:
+must conform to `SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0`:
 
 - `--json` / `--format` / structured JSON error envelope on stderr
 - `schema` and `describe` sub-commands
@@ -84,7 +84,7 @@ Zamak/
 ├── CHANGELOG.md            # Keep-a-Changelog + ISO 8601 dates
 ├── CLAUDE.md               # Claude-Code-specific context
 ├── AGENTS.md               # (this file)
-├── SKILL.md                # Steelbore skill manifest
+├── SKILL.md                # Spacecraft Software skill manifest
 ├── CONTRIBUTING.md         # human-contributor guide
 ├── zamak-core/             # shared no-std library
 ├── zamak-cli/              # host CLI (dual-mode)

CHANGELOG.md

@@ -12,6 +12,16 @@ All dates use ISO 8601 format (YYYY-MM-DD).
 
 ## [Unreleased]
 
+### Changed
+
+- `zamak-test-kernel` emits a `KERNEL_ENTRY tsc=<u64>` line on
+  the Limine-Protocol entry point, before the existing
+  `ZAMAK` / `LIMINE_PROTOCOL_OK` sentinels. Lets M6-3 Part 2
+  compute bootloader-overhead deltas by capturing the same
+  kernel under ZAMAK vs Limine v10.x and subtracting the two
+  absolute TSC values. Additive output — existing
+  `boot-smoke` / `linux-bzimage` sentinel asserts unaffected.
+
 ## [0.9.0] - 2026-04-28
 
 Closes M1-16: end-to-end BIOS Limine-Protocol kernel boot under
@@ -390,7 +400,7 @@ bare-metal perf validation.
   - `zamak-uefi::paging` — arch-dispatching `build(boot_services, kernel) -> u64` that returns the per-arch root-table physical address (PML4 on x86, L0 on AArch64, Sv48 root on RISC-V, PGDH on LoongArch)
   - `zamak-uefi::main` refactored: deleted `stub_entry` and all `#[cfg(target_arch = "x86_64")]` gates on the shared boot path. Single arch-neutral entry point now dispatches through `paging::build` and `handoff::jump_to_kernel`. `cargo check --target aarch64-unknown-uefi` and `riscv64gc-unknown-none-elf` both clean.
   - `Permissions::KERNEL_LOAD_AREA` — RWX coarse preset for kernel-image mapping parity across arches until per-PHDR splitting is implemented
-- **SFRS dual-mode CLI** — `zamak-cli` now conforms to `SB-SFRS-STEELBORE-CLI v1.0.0`:
+- **SFRS dual-mode CLI** — `zamak-cli` now conforms to `SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0`:
   - Global flags: `--json`, `--format <human|json|jsonl|yaml|csv|explore>`, `--fields`, `--dry-run`, `--verbose`, `--quiet`, `--color`, `--no-color`, `--yes`, `--force`, `--print0`
   - JSON envelope `{metadata:{tool,version,command,timestamp}, data:...}` via `OutputPolicy::emit`
   - Structured error envelope on stderr (`error.code/exit_code/message/hint/timestamp/command/docs_url/io_kind`) with stable `UPPER_SNAKE_CASE` codes
@@ -408,7 +418,7 @@ bare-metal perf validation.
 - Context files at `Zamak/` repo root: `CLAUDE.md`, `AGENTS.md`, `SKILL.md`, `CONTRIBUTING.md`
 - Integration test matrix in `zamak-cli/tests/sfrs_conformance.rs` covering exit codes, TTY/non-TTY, `AI_AGENT=1`, `--dry-run`, control-char rejection, UTF-8 encoding, ANSI suppression, JSON Schema shape, `describe` enumeration
 - Crate rename: `libzamak` -> `zamak-core`, `zamak-loader` -> `zamak-uefi` (PRD §4.1)
-- Converted all `.asm` files to `global_asm!` in Rust source files (Steelbore §3.2)
+- Converted all `.asm` files to `global_asm!` in Rust source files (Spacecraft Software Standard §3.2)
 - Added `rustfmt.toml` project formatting configuration
 - Added `deny.toml` for `cargo-deny` license and CVE auditing
 - Added `CHANGELOG.md` (Keep a Changelog format)

CLAUDE.md

@@ -13,8 +13,8 @@ needs to avoid re-discovering them from scratch.
 
 **ZAMAK** is a Rust rewrite of the Limine bootloader targeting BIOS
 and UEFI on x86-64, AArch64, RISC-V 64, and LoongArch64. It is the
-second project of the **Steelbore** ecosystem. The canonical spec is
-`../ZAMAK_Bootloader_PRD_v1.3.docx.md` (SB-PRD-ZAMAK-001 v1.3.0).
+second project of the **Spacecraft Software** ecosystem. The canonical spec is
+`../ZAMAK_Bootloader_PRD_v1.3.docx.md` (SS-PRD-ZAMAK-001 v1.3.0).
 Implementation status lives in `../TODO.md`.
 
 ## Workspace layout
@@ -32,22 +32,72 @@ Multi-crate Cargo workspace rooted at `Zamak/Cargo.toml`:
 | `zamak-cli` | Host CLI (install, enroll-config, sbom, schema, describe, completions) |
 | `zamak-theme` | TOML theme parser |
 | `zamak-test` | QEMU integration-test harness |
-| `zamak-test-kernel` | Minimal Limine-Protocol test kernel |
 | `zamak-macros` | Proc-macros (`#[zamak_unsafe]`) |
 
-## Build / test commands
+`zamak-test-kernel` and `zamak-linux-stub-kernel` are *excluded*
+from the workspace (`Cargo.toml:22`) so their nightly +
+`build-std` configs apply cleanly. Build explicitly with
+`cargo +nightly build --manifest-path <crate>/Cargo.toml --release`.
 
-- `RUSTFLAGS='' cargo build` — default workspace build. `RUSTFLAGS=''`
-  prefix is required because the shell env may carry
-  `-C target-cpu=x86-64-v3`, which breaks RISC-V / LoongArch cross builds.
-- `RUSTFLAGS='' cargo test -p zamak-core -p zamak-theme -p zamak-cli` — unit tests
-- `RUSTFLAGS='' cargo test --workspace` — full workspace
-- `RUSTFLAGS='' cargo clippy --lib -- -D warnings` — lint
-- `cargo +nightly miri test -p zamak-core --lib` — Miri (nightly component required)
-- `./zamak-test/build-images.sh && RUSTFLAGS='' cargo run -p zamak-test -- --suite boot-smoke` — QEMU smoke
-- `cargo build --features tui -p zamak-cli` — CLI with TUI explore mode
+## Build / test commands
 
-## Steelbore Standard invariants
+Mirror of what CI runs (`.github/workflows/ci.yml`):
+
+```sh
+cargo fmt --all -- --check                                       # fmt
+cargo clippy -p zamak-core -p zamak-proto -p zamak-theme \
+             -p zamak-cli  -p zamak-macros -p zamak-test \
+             --all-targets -- -D warnings                        # host-runnable crates only
+cargo test  -p zamak-core --lib -p zamak-theme -p zamak-cli      # unit
+cargo test  -p zamak-core --test proptests                       # property
+cargo miri-test                                                  # alias → +nightly miri test -p zamak-core --lib
+cargo deny check                                                 # licenses + advisories
+cargo build -p zamak-uefi --target <T> \
+            -Z build-std=core,alloc,compiler_builtins \
+            -Z build-std-features=compiler-builtins-mem          # cross, T ∈ {x86_64-unknown-uefi,
+                                                                 #                 aarch64-unknown-uefi,
+                                                                 #                 riscv64gc-unknown-none-elf,
+                                                                 #                 loongarch64-unknown-none}
+./zamak-test/build-images.sh && \
+  cargo run -p zamak-test -- --suite <S> --timeout 60            # S ∈ {boot-smoke, linux-bzimage, asm-verification}
+cargo build --features tui -p zamak-cli                          # CLI with TUI explore mode
+```
+
+Freestanding crates (`zamak-uefi`, `zamak-bios`, `zamak-stage1`,
+`zamak-decompressor`) are not in the clippy / unit-test sets; they
+build under `cross` against their real targets.
+
+### Local build prerequisites
+
+- **`RUSTFLAGS=''` prefix** is required if your shell exports flags
+  incompatible with the cross targets — `-C target-cpu=x86-64-v3`
+  is the common culprit, and `-Clink-arg=-z -Clink-arg=pack-relative-relocs`
+  also breaks the UEFI link step (`rust-lld` in PE-COFF mode mis-parses
+  `-z` as an unknown PE option). CI sets `RUSTFLAGS: -D warnings`
+  globally in the workflow env (`ci.yml:25`).
+- **`cc` / `objcopy` / `ld` not on PATH** (e.g. plain login shell
+  on NixOS, no `nix develop` / `nix-shell` active): wrap cargo
+  invocations with
+  `nix shell nixpkgs#gcc nixpkgs#binutils -c <cmd>`. The error
+  surfaces as `error: linker 'cc' not found` from the
+  `compiler_builtins` build script and blocks every `-Zbuild-std`
+  build.
+- **`mtools` + `sfdisk` + `objcopy`** are required by
+  `zamak-test/build-images.sh` (BIOS disk image assembly). CI
+  installs them via `apt-get install -y qemu-system-x86 ovmf mtools`;
+  locally on NixOS they're already on the system PATH except for
+  `objcopy` (`binutils`).
+
+### CI jobs
+
+`fmt`, `clippy`, `test` (3-target matrix: Linux x86-64, Linux
+AArch64, macOS AArch64), `freebsd` (14.x via
+`vmactions/freebsd-vm`), `miri`, `deny`, `cross` (4 UEFI/none
+targets), `size-gate` (≤ 120 % of Limine v10.x baseline, §6.1),
+`qemu-smoke` (`boot-smoke` + `linux-bzimage`), `asm-verification`,
+and `sbom` (main-only, SPDX 2.3 via `zamak-cli sbom`).
+
+## Spacecraft Software Standard invariants
 
 These are **non-negotiable**. Violating any one of them is a blocking
 defect.
@@ -69,10 +119,14 @@ defect.
 - **Newtype address wrappers** (`PhysAddr`, `VirtAddr`, `Cr3Value`,
   `MairValue`, `SatpValue`) and `checked_add`/`checked_sub`/`div_ceil`
   on all address arithmetic.
+- **Binary-size budget.** Each bootloader artifact (`BOOTX64.EFI`,
+  `BOOTAA64.EFI`, `BOOTRISCV64.EFI`, `zamak-bios.sys`) must stay
+  ≤ 120 % of the Limine v10.x baseline. CI `size-gate` enforces
+  this; baselines live inline in `.github/workflows/ci.yml`.
 
 ## CLI: SFRS dual-mode contract
 
-`zamak-cli` conforms to `SB-SFRS-STEELBORE-CLI v1.0.0`:
+`zamak-cli` conforms to `SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0`:
 
 - **Global flags** (every sub-command): `--json`, `--format <fmt>`,
   `--fields`, `--dry-run`, `--verbose`, `--quiet`, `--color`,
@@ -101,10 +155,34 @@ defect.
   (use `zamak-test` harness for those).
 - Keep commits small and scoped — one SFRS-N or M-N item per commit
   when possible.
+- Every user-facing change updates `CHANGELOG.md` and `TODO.md` in
+  the *same* commit (per `CONTRIBUTING.md`). Releases roll
+  `[Unreleased]` → `## [vX.Y.Z] - YYYY-MM-DD`.
+
+## Companion docs
+
+- `AGENTS.md` — safety-critical crates (`arch`, `entry`, `mbr`,
+  `trampoline`, `handoff`, `protocol`) and the
+  `zamak describe --json` live capability manifest.
+- `SKILL.md` — agent-facing CLI patterns (`--dry-run --json`
+  preview, non-TTY → `--yes` / `--force`, `--format explore` TUI
+  fallback).
+- `CONTRIBUTING.md` — PR checklist, unsafe-block contract format,
+  and the `CHANGELOG.md` + `TODO.md` co-update rule above.
 
 ## Current milestone
 
-See `../TODO.md` for the authoritative live status. At time of
-writing ZAMAK is past M0–M5 milestone scope; remaining work is
-gated on tagged release, FreeBSD CI runner, bare-metal perf
-validation, and the SFRS dual-mode CLI follow-ons.
+See `../TODO.md` for the authoritative live status. v0.9.0 closed
+M1-16 (BIOS Path B → end-to-end Limine boot) and the FreeBSD CI
+runner (now via `vmactions/freebsd-vm@v1` — `ci.yml:89`). The two
+known partials gating v1.0 are:
+
+- **M6-1 LoongArch UEFI** — blocked on rustc upstream
+  (`loongarch64-unknown-uefi` target not yet stable).
+- **M6-3 Part 2** — bare-metal perf baseline against Limine v10.x.
+  Part 1 (TSC instrumentation) shipped in v0.8.5; the hardware
+  capture is the open work. Staging tree lives at
+  `dist/perf-baseline/` (gitignored). The
+  `zamak-test-kernel` emits a `KERNEL_ENTRY tsc=<u64>` line on
+  every Limine-Protocol entry so ZAMAK and Limine can be compared
+  with the same kernel, same physical TSC.

CONTRIBUTING.md

@@ -5,7 +5,7 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 
 # Contributing to ZAMAK
 
-Thanks for your interest in ZAMAK — the Steelbore-ecosystem Rust
+Thanks for your interest in ZAMAK — the Spacecraft Software ecosystem Rust
 rewrite of the Limine bootloader. This document is the human
 contributor on-ramp; `CLAUDE.md`, `AGENTS.md`, and `SKILL.md` cover
 the machine / agent side.
@@ -29,7 +29,7 @@ the machine / agent side.
 ## Development setup
 
 ```
-git clone https://codeberg.org/steelbore/zamak
+git clone https://codeberg.org/spacecraft-software/zamak
 cd zamak/Zamak
 RUSTFLAGS='' cargo build
 RUSTFLAGS='' cargo test --workspace
@@ -83,7 +83,7 @@ Before opening a PR:
 
 ## CLI-specific expectations
 
-`zamak-cli` conforms to `SB-SFRS-STEELBORE-CLI v1.0.0`. New sub-
+`zamak-cli` conforms to `SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0`. New sub-
 commands must:
 
 1. Register a `CommandSpec` in `src/schema.rs`.
@@ -100,6 +100,6 @@ command appears in the manifest.
 
 ## Code of Conduct
 
-Be kind. Assume good faith. The Steelbore project values rigour
+Be kind. Assume good faith. Spacecraft Software values rigour
 over speed and correctness over cleverness; feedback in that spirit
 is always welcome.

SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: zamak
-description: ZAMAK bootloader host CLI — install stage1 MBR + stage2, enroll config BLAKE2B hashes into UEFI binaries, generate SPDX 2.3 SBOMs. Dual-mode (human + agent) per SB-SFRS-STEELBORE-CLI v1.0.0.
+description: ZAMAK bootloader host CLI — install stage1 MBR + stage2, enroll config BLAKE2B hashes into UEFI binaries, generate SPDX 2.3 SBOMs. Dual-mode (human + agent) per SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0.
 license: GPL-3.0-or-later
-project: Steelbore
+project: Spacecraft Software
 component: Zamak
 version: 0.1.0
 entry_points:
@@ -135,6 +135,6 @@ zamak schema install --json | jq .
 
 - `../ZAMAK_Bootloader_PRD_v1.3.docx.md` — full product spec
 - `../TODO.md` — live implementation status
-- `../steelbore-dual-mode-cli-sfrs.docx` — CLI framework SFRS v1.0.0
+- `../spacecraft-software-dual-mode-cli-sfrs.docx` — CLI framework SFRS v1.0.0
 - `zamak describe --json` — live capability manifest (authoritative
   at runtime)

TODO.md

@@ -5,7 +5,7 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 
 # ZAMAK Implementation Status — TODO
 
-**Reference:** `ZAMAK_Bootloader_PRD_v1.3.docx.md` (SB-PRD-ZAMAK-001 v1.3.0)
+**Reference:** `ZAMAK_Bootloader_PRD_v1.3.docx.md` (SS-PRD-ZAMAK-001 v1.3.0)
 **Generated:** 2026-04-21 (updated)
 **Current milestone target:** M6 — LoongArch64 + Polish (due 2027-06-01). M1–M5 functionally complete; remaining gates are release-tagging, CI artifact confirmation, and rustc upstream LoongArch-UEFI support.
 
@@ -33,7 +33,7 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 | M0-8 | `[✓]` | Create `zamak-stage1` as a proper Cargo crate (512-byte MBR, pure `global_asm!`, own linker script + target JSON) |
 | M0-9 | `[✓]` | Create `zamak-decompressor` crate (stage2 decompressor using `miniz_oxide`, loaded at 0x70000) |
 | M0-10 | `[✓]` | Create `zamak-cli` crate (host-side tool skeleton with subcommand stubs) |
-| M0-11 | `[✓]` | Create `zamak-theme` crate (theme parser with Steelbore palette defaults) |
+| M0-11 | `[✓]` | Create `zamak-theme` crate (theme parser with Spacecraft Software palette defaults) |
 | M0-12 | `[✓]` | Create `zamak-test` crate (QEMU integration test harness with serial capture) |
 | M0-13 | `[✓]` | Add `rustfmt.toml` project configuration |
 | M0-14 | `[✓]` | Add `deny.toml` for `cargo-deny` (license + CVE checks) |
@@ -43,7 +43,7 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 
 ---
 
-## Steelbore Standard Compliance — §3
+## Spacecraft Software Standard Compliance — §3
 
 ### §3.2 Inline Assembly — No Separate `.asm` Files (RESOLVED)
 
@@ -216,7 +216,7 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 
 ---
 
-## SFRS — Dual-Mode CLI (SB-SFRS-STEELBORE-CLI v1.0.0) — zamak-cli
+## SFRS — Dual-Mode CLI (SS-SFRS-SPACECRAFT-SOFTWARE-CLI v1.0.0) — zamak-cli
 
 | # | Status | Task |
 |---|--------|------|
@@ -228,10 +228,10 @@ SPDX-FileCopyrightText: 2026 Mohamed Hammad
 | SFRS-6 | `[✓]` | §3.5 / §4.3: structured JSON error envelope on stderr (`error.code`/`exit_code`/`message`/`hint`/`timestamp`/`command`/`docs_url`/`io_kind`) with stable `UPPER_SNAKE_CASE` codes via `error::emit` |
 | SFRS-7 | `[✓]` | §3.6: stdout=data / stderr=diagnostics split; `--fields a,b,c` projection via `Value::project`; `--format jsonl` streams each data row as one line |
 | SFRS-8 | `[✓]` | §3.7: noun-verb hierarchy with shared globals (`--json`, `--format`, `--fields`, `--dry-run`, `--verbose`, `--quiet`, `--color`, `--no-color`, `--yes`, `--force`, `--print0`); aliases hidden from `describe` / `schema` output |
-| SFRS-9 | `[✓]` | §4.2 / §4.4: Steelbore six-token palette via 24-bit ANSI (`output::Palette`); NO_COLOR / FORCE_COLOR / CLICOLOR / `--color={auto,always,never}` precedence; ANSI suppressed in every machine mode |
+| SFRS-9 | `[✓]` | §4.2 / §4.4: Spacecraft Software six-token palette via 24-bit ANSI (`output::Palette`); NO_COLOR / FORCE_COLOR / CLICOLOR / `--color={auto,always,never}` precedence; ANSI suppressed in every machine mode |
 | SFRS-10 | `[✓]` | §4.3: top-level JSON envelope `{metadata:{tool,version,command,timestamp}, data:...}` produced by `OutputPolicy::emit`; snake_case canonical; ISO 8601 strings; JSON null for missing values |
 | SFRS-11 | `[✓]` | §5: `--format explore` TUI via `ratatui` 0.29 + `crossterm` 0.28 behind Cargo feature `tui`; alt-screen; CUA + Vim keybinds (`↑↓`/`jk`, `/` filter, `s` sort, Enter detail, `e` export); TTY + non-agent guard with JSON fallback. Feature build verified clean (`cargo check --features tui`); all 95 zamak-cli tests still pass with the feature enabled |
-| SFRS-12 | `[✓]` | §6.3: `CLAUDE.md`, `AGENTS.md`, `SKILL.md`, `CONTRIBUTING.md` at `Zamak/` repo root per Steelbore context-file format |
+| SFRS-12 | `[✓]` | §6.3: `CLAUDE.md`, `AGENTS.md`, `SKILL.md`, `CONTRIBUTING.md` at `Zamak/` repo root per Spacecraft Software context-file format |
 | SFRS-13 | `[✓]` | §7.2: `validate` module — path canonicalization + allow-list (`safe_path`), control-byte rejection (`reject_control_chars`), numeric bounds (`check_bounds`), `--yes`/`--force` required for destructive ops in non-TTY (`confirm_destructive`) |
 | SFRS-14 | `[✓]` | §8.1 / §8.4: POSIX text records; `--print0` / `-0` global flag wired; `zamak completions <shell>` sub-command emits bash / zsh / fish / nushell scripts |
 | SFRS-15 | `[✓]` | §8.3: PowerShell-friendly JSON — single document (not NDJSON unless explicit), single-line stderr errors (`to_compact`), UTF-8 without BOM, Windows startup sets console CP 65001 via `SetConsoleOutputCP` |