Skip to content

Docs: hyp codex repair and hyp report delete <rec-id> in the CLI reference - #3013

Merged
HypForge merged 2 commits into
masterfrom
hypforge/docs-cli-1530
Nov 17, 2026
Merged

HypForge merged 2 commits into
masterfrom
hypforge/docs-cli-1530

Conversation

@HypForge

@HypForge HypForge commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Docs only. Entries due with v1.53.0, written against master 19b2872.

  • docs/CLI_REFERENCE.md: new "Repair saved Codex chats" section for hyp codex repair (--dry-run, apply, --restore <backup-path>, --codex-bin, --json), and a codex ...: @hypaware/codex line in the plugin-owned family list.
  • docs/CLI_REFERENCE.md: the hyp report delete <rec-id> form (second usage line, warning, and the recommendation-id paragraph). Only the wording that is true before hypaware-server Remove redundant CLI flag spellings #1707 deploys; on today's server the command always refuses and prints the three-argument form, which the paragraph says. The report recommend, list --recommendations, get and fix changes wait for that deploy.
  • docs/integrations/codex-cloud.md: the Requirements paragraph now says that on macOS the collector also finds the Codex CLI bundled with the ChatGPT app (Fix Codex Cloud capture with the ChatGPT-bundled CLI on macOS #2983).

Backups: the entry says what provider_repair.js does. Each backup is a full copy of the affected chats and the Codex state database. A repair that stops before it starts applying changes removes its backup; from that point on the backup stays, even if the repair fails or is rolled back, and no other code removes one.

Not included: the hyp status examples in docs/CLI.md and docs/TROUBLESHOOTING.md. They also lack the Version and Gateway lines, so they should be refreshed from a real 1.53.0 run rather than edited by hand.

Do not merge before npm shows 1.53.0.

Checks: npm test passes (9731 pass, 0 fail, 9 skipped).

…rence

Add a CLI_REFERENCE entry and family line for hyp codex repair, the
recommendation-id form of hyp report delete (the part that is true before
the server stores standalone recommendations as their own records), and
the ChatGPT-bundled Codex CLI to the Codex Cloud requirements.
A backup is removed only if the repair stops before it starts applying
changes. Also rewrap one long line in the restore paragraph.
@HypForge

Copy link
Copy Markdown
Contributor Author

Final review at head 34cff7f26be7d9aba2a9d87604ba64def29eda9e: LOW.

Docs only: docs/CLI_REFERENCE.md and docs/integrations/codex-cloud.md. Every sentence was checked against the code at master 19b28728 (v1.53.0).

hyp codex repair (hypaware-core/plugins-workspace/codex/src/provider_repair.js)

  • Usage matches the command's own (:628). --restore with --dry-run, or an unknown flag, exits 2 (:645-652).
  • --dry-run counts and changes nothing (:125).
  • Apply refuses while a codex, codex-cli or chatgpt process runs (:346-351).
  • A repair backs up each affected chat file (:158) and each state database with affected rows (VACUUM INTO, :179) into a new backup-* directory. It changes hypaware to openai (:205-207) and prints the backup path (:677).
  • Custom routes and profiles are refused (validateCodexRepairRoute, :330-342).
  • Deleted chat files are counted and left alone (:413-417, :676). Nothing to repair makes no backup (:125). An interrupted repair is refused with the --restore command (:617-618).
  • Restore:
    • needs Codex closed;
    • refuses another Codex home (:248, :252);
    • refuses a chat changed since the repair (:532) and changed metadata (:274).
  • The --codex-bin default (:691-702), --json (:673) and the exit codes (0, 1 at :686, 2) match.
  • Backup removal, fixed in this head. The catch deletes the backup only when the failure comes before publishing is set at :192 (:223). From there on it keeps it, including after a rollback (:224-228). That is the new sentence. The first wording missed a failure between :192 and the first rename at :198, which keeps the full backup. A failure at the last running check (:190) deletes a finished backup, which the new wording also covers.
  • No other code removes hypaware-provider-repair (grep on master: only the help text at codex/src/index.js:330).
  • The link to integrations/codex.md#reopen-chats-saved-with-gateway-capture resolves.

hyp report delete <rec-id> (src/core/cli/report_commands.js)

  • The text is DOC-2989-2990 edit 1 only; the report recommend entry is unchanged.
  • A lone id is the record form (:1786). One inside a report prints the three-argument command and returns 1 (:1813-1817). An unknown id returns 1 (:1321-1327).
  • It is true before hypaware-server Remove redundant CLI flag spellings #1707 deploys. Server master 3a01876c always answers the resolve route with the report (routes-reports.js:1066-1092), so today every id gets the whole-report refusal.

Codex Cloud (codex-cloud/src/cloud-auth.js:51-57): on macOS the helper PATH appends the ChatGPT app's bundled CLI, ~/Applications and then /Applications, after the existing PATH, as the sentence says.

Checks

  • Nothing under hypaware-core/skills/, no report or Ask prompt text, no tool description.
  • No U+2014, U+2028 or NUL in the diff. No attribution lines.
  • The delta from 8b2be2bb is one commit to docs/CLI_REFERENCE.md: the backup sentence and a re-wrap of the restore paragraph.
  • CI at this head, when checked: LLP required, typecheck, duplicate-numbers and cross-branch-numbers pass. test (22/24/26), test-windows and langgraph were still running.

Lines

  • Server-suite gate: not applicable. The PR is docs only, with no CLI command, MCP codec, tool schema, error code or contract.js change.
  • CPU and memory: no effect (docs only).
  • Privacy: LOW (LLP 0015 scale). The page says each backup is a full local copy of the affected chats and of Codex's state database, kept until the user deletes it, and names the one case where a repair removes it.
  • Rating: LOW.

@HypForge

Copy link
Copy Markdown
Contributor Author

Landing note (HypForge orchestrator): enqueuing at 34cff7f. Docs only, HypForge's own follow-up to the v1.53.0 release, so it lands on a clean LOW review with no human ask.

  • What it adds: the CLI reference entries for hyp codex repair and hyp report delete <rec-id>, and the macOS note that Codex Cloud capture also finds the Codex CLI bundled with the ChatGPT app. All three describe what 1.53.0 already does.
  • Review: LOW, clean, at this exact head (final comment above, 6937985953). One sentence was corrected during review: the page first said a repair that fails before changing any chat removes its backup; the backup, a full copy of the chats, is in fact kept from the moment the repair starts applying changes.
  • Server-suite gate: not applicable, docs only. CPU and memory: no effect. Privacy: LOW.
  • Timing: nothing was enqueued on this repo while the release PR was open or before npm showed 1.53.0 (published 04:01:15Z on 2026-11-17).
  • Guard: open, not a draft, CLEAN, every check green including test-windows, no release PR open.
  • Left out on purpose: the hyp status examples, which need a real 1.53.0 run; and the hyp report delete wording that is true only after hypaware-server Remove redundant CLI flag spellings #1707 deploys.

@HypForge
HypForge added this pull request to the merge queue Nov 17, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 17, 2026
@HypForge

Copy link
Copy Markdown
Contributor Author

Queue note (HypForge orchestrator): the merge queue dropped this PR at 04:21Z. One job failed in the merge-group run, test (26), on test/core/daemon-port-conflict-retry.test.js:410 ("file descriptors grow across failed boots", 26 !== 25). This PR changes two files under docs/, and the same test passed on this head's own run minutes earlier, so it is filed as a flaky test, #3014. The head is unchanged and the guard passes again, so it is enqueued once more at the same head.

@HypForge
HypForge added this pull request to the merge queue Nov 17, 2026
Merged via the queue into master with commit 10f1003 Nov 17, 2026
10 checks passed
@HypForge
HypForge deleted the hypforge/docs-cli-1530 branch November 17, 2026 04:27
@HypForge

Copy link
Copy Markdown
Contributor Author

Merged (HypForge orchestrator) as 10f1003 at 04:27:47Z on 2026-11-17, on the second pass through the merge queue. CI on the merge commit is green. The pages on hypaware.ai are built when the site next deploys, so these entries show there after that deploy, not yet.

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