Skip to content

chore(aethyme): redeploy 0.8.26 guidance #196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
schiste merged 1 commit into from
Oct 9, 2026
Merged

chore(aethyme): redeploy 0.8.26 guidance #196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions .codex/skills/aethyme/references/broker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,29 @@ blocked.
aethyme broker advanced ship execute --entry <promoted-entry-id> --confirm <full-publication-sha>
```

By default, the selected entry is a prefix boundary: every earlier
promoted-but-unpublished entry ships with it. In promote-mode repositories,
`--only` can publish one independent entry without changing that default:

```bash
aethyme broker advanced ship plan --entry <promoted-entry-id> --only
aethyme broker advanced ship execute --entry <promoted-entry-id> --only --confirm <full-publication-sha> --plan <sha256>
```

The plan refuses when an earlier unshipped entry is required by ancestry,
changed-path overlap, or a declared `Depends-On` trailer. Otherwise it gates
the exact tree made from the remote default branch plus only the selected
entry. Planning does not move refs, though it may record gate results in the
local cache; execution requires the reviewed plan digest. After publication,
the broker rebases the remaining pending entries onto the published commit
in integration and re-runs gates only for replayed trees that changed.
Review that reconciliation report. If it refuses or cannot apply safely,
use `aethyme broker advanced integration reconcile --upstream <published-sha> --dry-run`
and follow its reviewed apply plan. `broker main reconcile plan/apply` remains
the separate operation for advancing the local default checkout from
integration; independent publication does not mark the other queue entries
shipped or change their promotion order.

Prefer this reviewed broker ship workflow over a raw push. Never infer
publication authority from permission to edit, submit, or promote.
Without publication authority, stop after submit and report the promoted
Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Agent Instructions
<!-- AETHYME-GENERATED: version=0.8.24; policy-sha256=ebcafce816f060cc343daa82675421f2a19781d4175918aa596ba0392213bfc6 -->
<!-- AETHYME-GENERATED: version=0.8.26; policy-sha256=ebcafce816f060cc343daa82675421f2a19781d4175918aa596ba0392213bfc6 -->

Generated by Aethyme; do not edit. Customize `.aethyme/overrides/agents.json`
(policy) or `.aethyme/overrides/onboarding.json` (orientation), then run
Expand Down
2 changes: 1 addition & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Agent Instructions
<!-- AETHYME-GENERATED: version=0.8.24; policy-sha256=ebcafce816f060cc343daa82675421f2a19781d4175918aa596ba0392213bfc6 -->
<!-- AETHYME-GENERATED: version=0.8.26; policy-sha256=ebcafce816f060cc343daa82675421f2a19781d4175918aa596ba0392213bfc6 -->

Generated by Aethyme; do not edit. Customize `.aethyme/overrides/agents.json`
(policy) or `.aethyme/overrides/onboarding.json` (orientation), then run
Expand Down
Loading