Luigit
repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by admin

.system/plans/PX-PLAN-2_9FRWV0-relop-runtime-retirement/index.md

Raw
Rendered preview

id: PX-PLAN-2_9FRWV0 type: plan title: Relop Runtime Retirement spec: PX-SPEC-G_MQBERR status: draft

Outcome

Remove Relop from supported source/build/runtime surfaces without removing peer-review practice or rewriting user history. Implements Relop Retirement. Integration prerequisite: Peer Review Skill Delivery has produced a usable review route. No runtime prerequisite on Hornets or Ask events.

Cross-plan dependencies

Solid arrows are delivery prerequisites; dashed arrows are optional capability integrations. These are feature outputs, not System board states.

flowchart TB
  P["Peer-review skill available"] -->|"integration gate"| R["Relop absent from installation"]
  H["Claude delegation and bridge"] --> C["Codex parity"]
  A["Ask question service"] -.->|"optional questions"| H
  A -.->|"optional questions"| C
  H -.->|"optional transport"| P
  C -.->|"optional transport"| P

The graph links Ask service, Claude delegation, and Codex parity without making them prerequisites for retirement.

Ordered behaviors

  1. Install and run Pi without the Relop extension. First confirm the peer-review skill's supported discovery and invocation path; do not remove the only active review route. Remove extensions/relop/ package/runtime/resources/tests/tasks and its root TypeScript reference in tsconfig.json. Remove Relop from explicit lists in scripts/codegen/targets.json; regenerate owning outputs through //:codegen. Refresh root lock/workspace metadata through //:lock and //:install, retaining unrelated changes and current root dependency ranges. Fresh root installation and package discovery must neither load nor advertise the Relop tool.

  2. Upgrade an existing collection without stale live registration. Trace scripts/build/build.ts, collection.ts, scripts/extensions.ts, and release packaging for source-driven enumeration and stale-output behavior. Adjust only the path needed to keep a previously built dist/relop out of active collection/release metadata; clean that obsolete owned build output deliberately rather than deleting unrelated dist content. Add a focused build/collection regression using a temporary source tree with a removed extension and stale generated package. Verify both fresh and previously built root distributions expose the peer-review skill and no Relop tool, task, or setting declaration.

  3. Preserve history and explain discontinued behavior. Remove obsolete active requirements to invoke Relop, including its injected tool guidance; scan prompts/skills/build registrations rather than rewriting historical mentions. Update root user-facing documentation for retired relop settings and non-resumable old loops; record implementation history only in root CHANGELOG.md. Leave user settings, saved sessions, historical custom entries, prior specifications, and internal changelog records unchanged. Verify unrelated PiPi, Dilemma, and Ask registration and representative behavior still work after removal.

Boundaries

The original Relop specification remains historical. No alias or replacement tool recreates Relop's state machine, pool, immutable-scope gate, or convergence claims. Root installation and collection generation remain source-owned; no user configuration migration or new standalone release unit. Any dependency removal requires actual ownership evidence; shared dependencies remain centrally reproducible.

Verification

  • Scoped search distinguishes active references from intentional history; record retained references and their reason.
  • Build/collection tests cover a fresh tree and an upgrade tree with stale Relop output.
  • Run root //:check and //:test once at integration, plus existing focused build/collection checks during iteration.
  • Build the affected collection and verify relocation/registration without recreating deleted extension-local tasks.
  • No live user-session edits, implicit publication, root CI, or unrelated E2E.

Exit criteria

  • Fresh and upgraded supported installations expose no Relop runtime, tool, active setting declaration, or automation registration.
  • Peer-review guidance resolves to the delivered skill through existing delegation.
  • Historical documents, user settings, and recorded reviews remain intact; old-loop discontinuation is explained without a clean claim.
  • Unrelated PiPi, Dilemma, Ask, and root installation behavior pass representative verification.
  • No dependency on Hornets or Ask question events is introduced.
---
id: PX-PLAN-2_9FRWV0
type: plan
title: Relop Runtime Retirement
spec: PX-SPEC-G_MQBERR
status: draft
---

## Outcome

Remove Relop from supported source/build/runtime surfaces without removing peer-review practice or rewriting user history.
Implements [Relop Retirement](../../specs/PX-SPEC-G_MQBERR-relop-retirement/index.md).
Integration prerequisite: [Peer Review Skill Delivery](../PX-PLAN-P4FMHCDS-peer-review-skill-delivery/index.md) has produced a usable review route.
No runtime prerequisite on Hornets or Ask events.

## Cross-plan dependencies

Solid arrows are delivery prerequisites; dashed arrows are optional capability integrations.
These are feature outputs, not System board states.

```mermaid
flowchart TB
  P["Peer-review skill available"] -->|"integration gate"| R["Relop absent from installation"]
  H["Claude delegation and bridge"] --> C["Codex parity"]
  A["Ask question service"] -.->|"optional questions"| H
  A -.->|"optional questions"| C
  H -.->|"optional transport"| P
  C -.->|"optional transport"| P
```

The graph links [Ask service](../PX-PLAN-NY2PMQWM-ask-question-service/index.md), [Claude delegation](../PX-PLAN-PIXXMV4M-hornets-claude-delegation/index.md), and [Codex parity](../PX-PLAN-2W7CNSCD-hornets-codex-parity-and-optional-bridges/index.md) without making them prerequisites for retirement.

## Ordered behaviors

1. **Install and run Pi without the Relop extension.**
   First confirm the peer-review skill's supported discovery and invocation path; do not remove the only active review route.
   Remove `extensions/relop/` package/runtime/resources/tests/tasks and its root TypeScript reference in `tsconfig.json`.
   Remove Relop from explicit lists in `scripts/codegen/targets.json`; regenerate owning outputs through `//:codegen`.
   Refresh root lock/workspace metadata through `//:lock` and `//:install`, retaining unrelated changes and current root dependency ranges.
   Fresh root installation and package discovery must neither load nor advertise the Relop tool.

2. **Upgrade an existing collection without stale live registration.**
   Trace `scripts/build/build.ts`, `collection.ts`, `scripts/extensions.ts`, and release packaging for source-driven enumeration and stale-output behavior.
   Adjust only the path needed to keep a previously built `dist/relop` out of active collection/release metadata; clean that obsolete owned build output deliberately rather than deleting unrelated dist content.
   Add a focused build/collection regression using a temporary source tree with a removed extension and stale generated package.
   Verify both fresh and previously built root distributions expose the peer-review skill and no Relop tool, task, or setting declaration.

3. **Preserve history and explain discontinued behavior.**
   Remove obsolete active requirements to invoke Relop, including its injected tool guidance; scan prompts/skills/build registrations rather than rewriting historical mentions.
   Update root user-facing documentation for retired `relop` settings and non-resumable old loops; record implementation history only in root `CHANGELOG.md`.
   Leave user settings, saved sessions, historical custom entries, prior specifications, and internal changelog records unchanged.
   Verify unrelated PiPi, Dilemma, and Ask registration and representative behavior still work after removal.

## Boundaries

The original [Relop specification](../../specs/PX-SPEC-R8L4Q2NV-relop-independent-review-loop/index.md) remains historical.
No alias or replacement tool recreates Relop's state machine, pool, immutable-scope gate, or convergence claims.
Root installation and collection generation remain source-owned; no user configuration migration or new standalone release unit.
Any dependency removal requires actual ownership evidence; shared dependencies remain centrally reproducible.

## Verification

- Scoped search distinguishes active references from intentional history; record retained references and their reason.
- Build/collection tests cover a fresh tree and an upgrade tree with stale Relop output.
- Run root `//:check` and `//:test` once at integration, plus existing focused build/collection checks during iteration.
- Build the affected collection and verify relocation/registration without recreating deleted extension-local tasks.
- No live user-session edits, implicit publication, root CI, or unrelated E2E.

## Exit criteria

- [ ] Fresh and upgraded supported installations expose no Relop runtime, tool, active setting declaration, or automation registration.
- [ ] Peer-review guidance resolves to the delivered skill through existing delegation.
- [ ] Historical documents, user settings, and recorded reviews remain intact; old-loop discontinuation is explained without a clean claim.
- [ ] Unrelated PiPi, Dilemma, Ask, and root installation behavior pass representative verification.
- [ ] No dependency on Hornets or Ask question events is introduced.