v1 release gate: hard-cut every deprecated alias before 1.0 (no transition path ships into v1) #1050

New issue

Closed

opened 2026-07-10 17:23:34 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 17:23:34 +00:00

Member

Context

Ward is on the run-up to its 1.0 release (currently on the v0.5xx line). v1 is the compatibility boundary: every alias, flag spelling, and env knob that today survives only as a deprecated / legacy / "kept for one release" transition path must be hard-removed before 1.0. No deprecated alias should ship into v1 - after the 1.0 tag, the canonical spelling is the only spelling.

This is a standing policy plus a tracked cutoff, distinct from the broad ward#1015 V1 deletion pass (a P3 "consult" sweep across many surfaces): this issue elevates the alias hard-cutoff specifically as a release gate for 1.0, and keeps the alias inventory current as new ones are minted.

Policy

Any compatibility alias is born with a v1 death date. Introducing one now (e.g. the --force -> --override-reservation alias in ward#1045) is fine as a transition aid, but it must be enumerated here and removed before 1.0.
At the 1.0 tag: no public or hidden parser accepts a removed spelling. Canonical concepts and spellings only.

Known deprecated aliases to cut (converge with ward#1015 §5)

ward#1015 section 5 ("Remove expired compatibility aliases") already enumerates the pre-existing set. Land that slice as its own unit ahead of the rest of #1015, and add the ones minted since:

qwen -> opencode
--driver, --engineer-driver -> --harness
deprecated workflow spellings -> canonical workflow values
--aws, --tailnet (and hidden --tailnet-mode compat-only behavior) -> config-driven capabilities
old environment-variable aliases, and the dead WARD_AGENT_SINK knob (ward#1015 §6)
broker acceptance of any removed flag spelling
--force -> --override-reservation (new, from ward#1045 - this transition alias must not outlive v1)

Acceptance

Every alias above is removed end to end: implementation, hidden fallbacks, broker acceptance, tests that exist only to preserve the old spelling, and docs / help text.
No deprecated alias is registered or silently accepted at the 1.0 tag.
Any alias introduced between now and 1.0 is added to this list with its canonical target, and cut before the tag.
ward#1015 §5 is either executed here or explicitly de-scoped there, so the alias set is tracked in exactly one place.

ward#1015 - the broad V1 deletion pass; §5 is the alias enumeration this gate executes and converges.
ward#1045 - introduces the --force -> --override-reservation alias this gate retires at v1.

## Context Ward is on the run-up to its **1.0 release** (currently on the v0.5xx line). v1 is the **compatibility boundary**: every alias, flag spelling, and env knob that today survives only as a deprecated / legacy / "kept for one release" transition path must be **hard-removed before 1.0**. No deprecated alias should ship **into** v1 - after the 1.0 tag, the canonical spelling is the only spelling. This is a standing policy plus a tracked cutoff, distinct from the broad `ward#1015` V1 deletion pass (a P3 "consult" sweep across many surfaces): this issue elevates the **alias hard-cutoff specifically** as a **release gate** for 1.0, and keeps the alias inventory current as new ones are minted. ## Policy * Any compatibility alias is born with a **v1 death date**. Introducing one now (e.g. the `--force` -> `--override-reservation` alias in `ward#1045`) is fine as a transition aid, but it must be enumerated here and removed before 1.0. * At the 1.0 tag: no public or hidden parser accepts a removed spelling. Canonical concepts and spellings only. ## Known deprecated aliases to cut (converge with ward#1015 §5) `ward#1015` section 5 ("Remove expired compatibility aliases") already enumerates the pre-existing set. Land that slice as its own unit ahead of the rest of #1015, and add the ones minted since: * `qwen` -> `opencode` * `--driver`, `--engineer-driver` -> `--harness` * deprecated workflow spellings -> canonical workflow values * `--aws`, `--tailnet` (and hidden `--tailnet-mode` compat-only behavior) -> config-driven capabilities * old environment-variable aliases, and the dead `WARD_AGENT_SINK` knob (`ward#1015` §6) * broker acceptance of any removed flag spelling * **`--force` -> `--override-reservation`** (new, from `ward#1045` - this transition alias must not outlive v1) ## Acceptance * Every alias above is removed end to end: implementation, hidden fallbacks, broker acceptance, tests that exist only to preserve the old spelling, and docs / help text. * No deprecated alias is registered or silently accepted at the 1.0 tag. * Any alias introduced between now and 1.0 is added to this list with its canonical target, and cut before the tag. * `ward#1015` §5 is either executed here or explicitly de-scoped there, so the alias set is tracked in exactly one place. ## Related * `ward#1015` - the broad V1 deletion pass; §5 is the alias enumeration this gate executes and converges. * `ward#1045` - introduces the `--force` -> `--override-reservation` alias this gate retires at v1.

coilyco-ops added the

headless

labels

2026-07-14 06:50:15 +00:00

coilyco-ops commented

2026-07-14 07:06:04 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1050 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-14T07:06:03Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1050 · branch issue-1050 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1050 · ward v0.667.0 · dispatched 2026-07-14T07:05:59Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.667.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1050` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T07:06:03Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1050` · branch `issue-1050` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1050` · ward `v0.667.0` · dispatched `2026-07-14T07:05:59Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.667.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-14 07:30:48 +00:00

v1 release gate: hard-cut every deprecated alias before 1.0 #1238

coilysiren closed this issue

2026-07-14 07:31:56 +00:00

coilysiren referenced this issue from a commit

2026-07-14 07:31:58 +00:00

v1 release gate: hard-cut every deprecated alias before 1.0 (#1238)

coilyco-ops commented

2026-07-14 07:32:24 +00:00

Author

Member

WARDED_WORKFLOW: #1238

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: direct, mechanical, and mostly stale-path removal. confidence: high surprises: the generated flag doc and a few lint nits still referenced the old surface. follow-ups: merge the PR and let the director record the done outcome.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1238 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: direct, mechanical, and mostly stale-path removal. confidence: high surprises: the generated flag doc and a few lint nits still referenced the old surface. follow-ups: merge the PR and let the director record the done outcome. </details>