Skip to content

feat(errors): PRO-UX.1 + PRO-UX.2 — Pro CLI error UX bridge + root-cause fix #775

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rafaelscosta merged 6 commits into from
May 21, 2026
Merged

feat(errors): PRO-UX.1 + PRO-UX.2 — Pro CLI error UX bridge + root-cause fix #775

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c22ea06
feat(errors): pro-error-registry extending defaultErrorRegistry [Stor…
rafaelscosta May 20, 2026
e860d56
feat(pro-cli): envelope bridge + warm render + OS-aware recovery [Sto…
rafaelscosta May 20, 2026
d9c8966
fix(installer): parse nested error envelope in pro-setup _request [St…
rafaelscosta May 20, 2026
6b1fdb3
chore(ids): register pro-error-registry in entity registry [Story PRO…
rafaelscosta May 20, 2026
6aa9233
chore(ids): regen entity-registry deterministically [Story PRO-UX.1]
rafaelscosta May 20, 2026
2df2f83
fix(pro-cli): null/non-object guards in renderError + pro-setup fallb…
rafaelscosta May 20, 2026
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
83 changes: 83 additions & 0 deletions .aiox-core/core/errors/pro-error-registry.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
// PRO-UX.1 / PRO-UX.2 — Pro-specific error registry for the AIOX Pro CLI.
// Extends the canonical error-governance infra (EPIC-AIOX-ERROR-GOVERNANCE):
// reuses AIOXError + ErrorRegistry, maps to EXISTING ErrorCategory values
// (no new categories — constants.js is Object.freeze), and mirrors the
// license-server ErrorCodes (no AIOX_ prefix — deliberate, validated by the
// /^[A-Z0-9_]+$/ regex in ErrorRegistry._normalizeDefinition).
//
// userMessage holds the warm G3-approved PT-BR copy (fallback when the server
// envelope omits message_pt). recovery holds actionable PT-BR steps.

const { ErrorRegistry } = require('./error-registry');
const { ErrorCategory, ErrorSeverity } = require('./constants');
Comment on lines +11 to +12

@coderabbitai coderabbitai Bot May 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win

Use absolute imports for core error modules.

Please switch these require('./...') statements to the project’s absolute import form to align with repository standards.

As per coding guidelines, **/*.{js,jsx,ts,tsx}: Use absolute imports instead of relative imports in all code.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.aiox-core/core/errors/pro-error-registry.js around lines 11 - 12, Replace
the local relative requires for ErrorRegistry and constants with the project's
absolute import style: change the require('./error-registry') and
require('./constants') calls to the repository's absolute module imports that
export ErrorRegistry, ErrorCategory, and ErrorSeverity, and ensure the top of
pro-error-registry.js imports those same symbols via the absolute paths used
elsewhere in the core errors modules; also update any other relative imports in
this file to match the absolute-import convention.


const PRO_ERROR_DEFINITIONS = Object.freeze([
{
code: 'SEAT_LIMIT_EXCEEDED',
category: ErrorCategory.PERMISSION, // license-server "auth says no" → permission
severity: ErrorSeverity.ERROR,
retryable: false,
exitCode: 13,
userMessage:
'Opa! Você já está usando o Pro no número máximo de máquinas. Pega o código de suporte aqui embaixo e fala com a gente que a gente libera rapidinho.',
recovery: [
'Pega o código de suporte abaixo',
'Cola no chat com o suporte',
'Depois que liberarem, roda o comando de instalação de novo',
],
},
{
code: 'NOT_A_BUYER',
category: ErrorCategory.PERMISSION,
severity: ErrorSeverity.ERROR,
retryable: false,
exitCode: 13,
userMessage:
'Hmm, sua licença Pro não está ativa no momento. Pega o código de suporte aqui embaixo e fala com a gente que resolvemos rapidinho.',
recovery: [
'Pega o código de suporte abaixo',
'Cola no chat com o suporte',
'Aguarda a verificação da sua compra',
],
},
{
code: 'REVOKED_KEY',
category: ErrorCategory.PERMISSION,
severity: ErrorSeverity.ERROR,
retryable: false,
exitCode: 13,
userMessage:
'Hmm, sua licença Pro não está ativa no momento. Pega o código de suporte aqui embaixo e fala com a gente que a gente verifica pra você.',
recovery: [
'Pega o código de suporte abaixo',
'Cola no chat com o suporte',
'Aguarda o retorno do financeiro',
],
},
{
code: 'RATE_LIMITED',
category: ErrorCategory.NETWORK, // throttling → network layer
severity: ErrorSeverity.WARNING,
retryable: true,
userMessage:
'Calma! Foram muitas tentativas em pouco tempo. Espera uns minutinhos e tenta de novo.',
recovery: ['Aguarda 5 minutos', 'Tenta o comando de novo'],
},
{
code: 'PRO_ARTIFACT_UNAVAILABLE',
category: ErrorCategory.EXTERNAL_EXECUTOR, // npm/tarball fetch → external executor
severity: ErrorSeverity.ERROR,
retryable: true,
userMessage:
'Tivemos um probleminha pra baixar o componente Pro. Limpa o cache e tenta de novo em alguns minutos que deve rolar.',
recovery: [
'Aguarda 5 minutos (o servidor pode estar reiniciando)',
'Roda `aiox install --recover-cache` para limpar o cache local',
'Tenta de novo',
],
},
]);

const proErrorRegistry = new ErrorRegistry(PRO_ERROR_DEFINITIONS);

module.exports = { proErrorRegistry, PRO_ERROR_DEFINITIONS };
Loading
Loading