Skip to content

governance: ReScript frontend trips package anti-pattern policy on main #43

@hyperpolymath

Description

@hyperpolymath

What

governance / Language / package anti-pattern policy job is failing on main (verified 2026-06-01):

```
❌ ReScript files detected - use AffineScript instead
'# hypatia:ignore cicd_rules/banned_language_file' pragma if intentional)
```

Source: estate language policy 2026-05-25 banned ReScript estate-wide in favour of AffineScript.

Impact

Where the ReScript is

`frontend/src/` per `.claude/CLAUDE.md` — quandledb's UI shell.

Options

A. Migrate frontend/src → AffineScript (clean, estate-aligned; tracked separately under standards#252 estate-wide TS/ReScript→AffineScript campaign).

B. `.hypatia-ignore` pragma for `frontend/src/.res`** (escape hatch; keeps governance green until A lands).

C. Hand-port a minimal AffineScript shell that boots the same JSON API (smaller scope than full migration; aligned with estate STEP 8 first Mode-A batch pattern — see panll#72 / affinescript#505).

Out-of-scope today

The current krl/quandledb/tangle audit explicitly excludes estate-wide ReScript migration. This issue records the debt so that the next maintenance pass can take it.

Acceptance

Either `.hypatia-ignore` covers `frontend/`, or the ReScript files are gone and replaced by AffineScript equivalents, and the governance check is green on `main` for two consecutive pushes.

See also

  • standards#252 (estate ReScript→AffineScript umbrella)
  • panll#72 (Mode-A pattern: pure modules port first; user-shell defers)
  • affinescript#508 (AS `pub` gap in user-modules ESM codegen — blocks Mode-B for now)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions