Skip to content

Keep publisher seed material outside version control (r2 recovery) - #9

Merged
lr00rl merged 2 commits into
integrationfrom
feat/zeus-task0018-seed-guard-carry-r2
Aug 4, 2026
Merged

Keep publisher seed material outside version control (r2 recovery)#9
lr00rl merged 2 commits into
integrationfrom
feat/zeus-task0018-seed-guard-carry-r2

Conversation

@lr00rl

@lr00rl lr00rl commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

TASK-0018 immutable-object recovery under Olympus rules/01 §3.1.

  • Supersedes Draft Keep publisher seed material outside version control #8 (00b50c042c5cfe89d672ff19dc426db520b7504a).
  • Recovery head: 9c4f595655928a17ef1932944ce2ce0b5bd730c0.
  • The tree, ordered parents, author/committer identity, and timestamps are byte-identical to the superseded commit. Only blank separators between Lore trailer fields were removed; native parsing changes from 1/8 to 8/8.
  • Delta from the reviewed integration base remains exactly .gitignore, 11 additions and no deletions.
  • Exact-head local gates: seed guard 8/8; Go 1.26.4 race suites; UI test command, typecheck, build, scan; released-server manifest validation; linux amd64/arm64 builds; deterministic packages byte-identical at the existing manifest digest; git diff --check; clean tree.

Draft pending fresh r2 owner review and GitHub CI. No r1 acknowledgement carries over.

lr00rl added 2 commits July 14, 2026 01:55
pluginsign reads a raw 32-byte Ed25519 seed from a file path. Nothing is
committed today, but the only thing between a publisher seed and main was one
`git add -A` — so ignore key material outright rather than relying on care.
Carry the reviewed signing-material ignore policy onto the current integration baseline while preserving all existing generated-artifact exclusions.

Constraint: TASK-0018 permits only the reviewed .gitignore guard and forbids key generation, signing, manifest edits, releases, or deployment.
Rejected: Recreate the ignore block as a new single-parent patch | preserving the reviewed branch as a two-parent merge retains provenance.
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Never weaken these patterns without re-running the seed-ignore guard and checking for signing material exposure.
Tested: 8/8 seed-ignore guard; Go 1.26.4 race tests; Node 22 npm ci/test/typecheck/build/verify; released-server manifest validator; linux amd64/arm64 builds; deterministic pluginpack digest parity.
Not-tested: GitHub-hosted CI pending push.
@lr00rl
lr00rl merged commit a2e355b into integration Aug 4, 2026
1 check passed
@lr00rl
lr00rl deleted the feat/zeus-task0018-seed-guard-carry-r2 branch August 4, 2026 09:24
@lr00rl

lr00rl commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Landed on integration as a2e355b8c89c269ec479177a0e4e7820be288aeb. The natural integration workflow passed on that exact merge commit; the published r1/r2 branches remain preserved for audit.

@lr00rl
lr00rl restored the feat/zeus-task0018-seed-guard-carry-r2 branch August 4, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant