Pass ALKANE_EMBEDDED_TOKEN (a repo Actions secret, a restricted read-only token
scoped to the alkane-os repo) into the release and candidate workflow builds, so
the published GUI can list the private alkane-os releases in its install picker
with no user setup. The source tree carries no secret (option_env!); the value
lives only in CI-built binaries.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
tools/report-relay is a dependency-free Python service. It takes the
JSON the app's Bug report button sends, validates it (type, text,
context and log sizes), scrubs the log a second time, rate-limits (5
per client IP and 60 in all per hour, 4 in flight), neutralises
@mentions, and files one issue in blueflare/alkane-toolkit with the
labels bug/ui/feature and from-app. It stores nothing and logs one
line per report without its text.
It runs on the Gitea host behind the shared nginx at
https://gitea.bluefla.re/alkane-report/ as the scoped alkane-reporter
bot (team alkane-reporters: issues write, code read, alkane-toolkit
only). See tools/report-relay/README.md. Its tests run in verify's
unit-test step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BdKQBRg6YCM1XXQCTnD5GF
https://blueflare.gitea.bluefla.re/alkane-toolkit/ is built from this repo
(gh-pages) after every main run: overview, manual, a quality dashboard and the
benchmark history, which no longer goes to alkane-benchmarks. The quality
grade is now Clippy/rustfmt plus the line-coverage band (the coverage badge's
own colour bands), not only the Clippy result, and main CI publishes the full
measurement (per-crate and per-file coverage, LOC per crate) as quality.json
for the dashboard. README badges link to their pages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AGENTS.md, HANDOFF.md, code-review-report.md, the implementation plan and the
aftermarket parity roadmap described the internal bench, its addresses and
in-house firmware; they now live in the private miner-firmware workspace and
are git-ignored here. The remaining docs and the fixture header no longer
point at them or at local infrastructure.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ci/sign-windows.sh signs alkane-toolkit.exe from Linux with jsign through
the blueflaresigning account (RFC 3161 timestamped), using the
least-privilege CI service principal alkane-toolkit-ci-signer. It is a
no-op until the repository variable AZURE_SIGNING_PROFILE names a
certificate profile; after that any signing failure fails the build.
- release.yml and next.yml sign before packaging; windows-native.yml checks
the signature with Get-AuthenticodeSignature on real Windows and requires
Valid once signing is on.
- CI image adds a Java runtime and a checksum-pinned jsign 7.6 (re-pinned);
windows-ci.sh fetches the same jar on older images.
- scripts/enable-windows-signing.sh turns signing on after Microsoft
approves the publisher identity validation: creates the PublicTrust
certificate profile, narrows the signer role to it, sets the variable.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The documentation- and workflow-only PR checks grepped every tracked file
for private-key headers, so the test fixtures inside vendored upstream
crates (openssl, rustls-pemfile, aws-lc) failed every such PR.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ci/windows-ci.sh is the one definition of every Windows step (toolchain,
clippy, build, tests and UI self-test under Wine, packaging, test bundle);
verify, release and next only call it.
- release.yml: a windows job builds, tests and packages
alkane-toolkit-vX.Y.Z-windows-x86_64.zip; the release job waits for it
and attaches the zip next to the Linux tarball. next.yml does the same
for -rc candidates, verify.yml runs the Windows gates on PRs.
- windows-native.yml (advisory, never gates a release) runs main's
cross-built unit tests and UI self-test on real Windows 11 through the
self-hosted VM runner (label alkane-windows).
- CI image: ci/images/alkane-ci.Dockerfile layers mingw-w64, Wine with a
ready prefix, the rustup target and a prebuilt wxMSW prefix on the
previously verified image; ci/images/build-image.sh pushes it and pins
the digest. wx prefix/cache scripts take a linux|windows argument.
- CI checks the wx-rs patch queue; versioning treats the GUI build script,
Windows resources and assets as release-relevant; the workflow contract
test covers the Windows gates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>