Build and deploy / build-and-deploy (push) Failing after 5s
Step 5 ships /practice/ and the six practice-area pages (construction,
technology, energy, insurance, shareholder, cross-border) from one route, and
adds the mechanical §4 gate Pouya ruled for.
check:claims — §4 Forbidden becomes a build error
scripts/check-claims.mjs greps dist/**/*.html for 10 patterns, each carrying
the incident that put it there. It strips <style> and non-JSON-LD <script>
first (a bare sweep for "leading" returned 26 hits, 25 of them
var(--leading-body)), self-tests every pattern against fixtures before
sweeping, and refuses a missing, empty or stale dist/. Wired into /build
Phase 5 and both deploy paths.
Q54 — six conduct undertakings publish, and §4 gains a third class
Conduct undertakings sit apart from credentials and offerings: the gate is
that Pouya said it in terms. The strings live in CONDUCT_UNDERTAKINGS so a
softening is one visible diff. (e) and (f) replace the third-person sentences
already on /arbitration/ rather than joining them.
Q49, Q50 recorded as rulings. §7 records the SES us-east-1 stray identity's
deletion. R11 holds typescript at its current major, with the peer-range
reason recorded.
Three facts corrected, two of them already shipped
- The LAT gloss said mediation "before filing and continuing after filing";
the Tribunal names mediation for "Before you apply" only and its second
sentence is about negotiation. An ellipsis in docs/01 had deleted it.
- "Connection allocation" is not an Ontario term.
- "The 2026 privacy statute" does not exist — Bill C-27 died without royal
assent. Struck from docs/03 rather than corrected in place.
ADR Chambers struck from /arbitration/ and from docs/01 item 3 (Pouya,
2026-08-30): the source establishes what the firm publishes, not that an
outside neutral can be appointed under its rules.
claims-auditor gains a second lens — for every quoted source, whether the
sentence beneath stays inside what the quotation establishes. Four shipped
defects had that shape and none of them is greppable.
CLAUDE.md gains a convention: never truncate the output of a check you intend
to believe. `npm run check | tail -3` returns warnings, hints and a blank line
and drops the errors line; it was reported as passing four times while
astro check was exiting 1 with 10 type errors.
Gates, exit status read directly, not through a pipe:
npm run check exit=0
npm run lint exit=0
npm run build exit=0
npm run check:claims exit=0
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5
84 lines
3.6 KiB
JavaScript
84 lines
3.6 KiB
JavaScript
// ESLint 10 flat config. Scope is deliberately small: this project targets zero
|
|
// client JavaScript (CLAUDE.md, AGENTS.md §7), so the only JS/TS here is build
|
|
// configuration, site data, and the occasional island. Rules exist to catch
|
|
// mistakes, not to impose style — Prettier owns formatting.
|
|
//
|
|
// `typescript-eslint` is here because .astro frontmatter IS TypeScript, so the
|
|
// plugin cannot parse a single component without it. It runs unconfigured for
|
|
// type-awareness on purpose: `astro check` already does the type checking, and
|
|
// duplicating it here would be slower and would disagree at the edges.
|
|
|
|
import js from '@eslint/js';
|
|
import globals from 'globals';
|
|
import tseslint from 'typescript-eslint';
|
|
import astro from 'eslint-plugin-astro';
|
|
|
|
export default [
|
|
{ ignores: ['dist/**', 'node_modules/**', '.astro/**', 'docs/reference/**'] },
|
|
|
|
js.configs.recommended,
|
|
...tseslint.configs.recommended,
|
|
...astro.configs.recommended,
|
|
...astro.configs['flat/jsx-a11y-recommended'],
|
|
|
|
// `no-undef` off for TYPESCRIPT ONLY, on typescript-eslint's own advice: it
|
|
// has no type information, so every ambient global is a false positive —
|
|
// Astro declares `ImageMetadata`, `astroHTML.JSX` and friends globally, and
|
|
// .astro frontmatter IS TypeScript. tsc catches a real undefined reference,
|
|
// which is what `npm run check` is for.
|
|
//
|
|
// NOT applied to .js/.mjs. `tsconfig.json` sets `allowJs` without `checkJs`,
|
|
// so plain JS is not type-checked by anything — turning the rule off there
|
|
// meant a typo like `procss.env.X` in astro.config.mjs passed lint silently.
|
|
{
|
|
files: ['**/*.ts', '**/*.astro'],
|
|
rules: { 'no-undef': 'off' },
|
|
},
|
|
|
|
{
|
|
files: ['**/*.{js,mjs,ts}', '**/*.astro'],
|
|
languageOptions: {
|
|
ecmaVersion: 2023,
|
|
sourceType: 'module',
|
|
globals: { ...globals.browser, ...globals.node },
|
|
},
|
|
rules: {
|
|
// A stray console.log in a static build is dead weight shipped to nobody.
|
|
'no-console': ['warn', { allow: ['warn', 'error'] }],
|
|
|
|
// `role="list"` on a <ul> is redundant to a spec reader and load-bearing
|
|
// in a browser: Safari drops list semantics from any list styled
|
|
// `list-style: none`, so VoiceOver stops announcing "list, 6 items".
|
|
// src/styles/global.css keys its own reset off `ul[role='list']` for
|
|
// exactly this reason. The rule is right in general; this is the one
|
|
// documented exception, and it is scoped to that single pairing.
|
|
'astro/jsx-a11y/no-redundant-roles': [
|
|
'error',
|
|
{ ul: ['list'], ol: ['list'] },
|
|
],
|
|
eqeqeq: ['error', 'always'],
|
|
'prefer-const': 'error',
|
|
'@typescript-eslint/no-unused-vars': [
|
|
'error',
|
|
{ argsIgnorePattern: '^_' },
|
|
],
|
|
},
|
|
},
|
|
|
|
// `scripts/` ARE CLI TOOLS, AND PRINTING IS THEIR OUTPUT. The `no-console`
|
|
// rule above is justified in this config as "a stray console.log in a static
|
|
// build is dead weight shipped to nobody" — which is a statement about the
|
|
// shipped bundle, and nothing in `scripts/` reaches it. `check-claims.mjs`
|
|
// exists to print what it matched: CLAUDE.md's rule is that a grep is not a
|
|
// finding until you read what it matched, so suppressing its output would
|
|
// defeat the tool. Scoped to this directory rather than disabled globally.
|
|
//
|
|
// ⚠️ IT MUST SIT AFTER THE BLOCK IT OVERRIDES. Flat config applies matching
|
|
// blocks in order, last one wins — placed above, this had no effect at all
|
|
// and `npm run lint` still reported all six warnings. Measured, not assumed.
|
|
{
|
|
files: ['scripts/**/*.{js,mjs}'],
|
|
rules: { 'no-console': 'off' },
|
|
},
|
|
];
|