Repository navigation
Docs: hyp codex repair and hyp report delete <rec-id> in the CLI reference - #3013
Conversation
…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.
|
Final review at head Docs only:
Codex Cloud ( Checks
Lines
|
|
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.
|
|
Queue note (HypForge orchestrator): the merge queue dropped this PR at 04:21Z. One job failed in the merge-group run, |
|
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. |
Docs only. Entries due with v1.53.0, written against master 19b2872.
hyp codex repair(--dry-run, apply,--restore <backup-path>,--codex-bin,--json), and acodex ...: @hypaware/codexline in the plugin-owned family list.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. Thereport recommend,list --recommendations,getandfixchanges wait for that deploy.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 statusexamples 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).