Build: Multilingual Release Gate v0.1.0

[proaiexpert]

Status

Product approved · Competitive research and implementation specification complete · Dedicated repository not yet created

Primary documents:

• Competitive analysis and MVP decision
• Implementation Specification V1

Approved product

Do not build another general SEO crawler.

Build a narrow product:

A framework-agnostic CLI and GitHub Action that validates an explicitly expected multilingual route map against built HTML or a deployment preview, then fails a pull request when canonical, hreflang, language-pair, sitemap, redirect, or indexing signals conflict.

Approved working name:

Multilingual Release Gate

Approved repository slug:

multilingual-release-gate

Approved v0.1.0 decisions

• TypeScript;
• Node.js 24;
• CLI and GitHub Action shipped together;
• MIT License for the standalone tool;
• deterministic rule engine with no AI dependency;
• no telemetry;
• built static directory and deployment-preview inputs;
• explicit YAML locale-cluster contract;
• terminal, JSON, Markdown, GitHub annotations, and job-summary outputs;
• bounded requests, protected-network controls, and no unrestricted crawling.

The MIT decision applies only to the standalone public tool. It does not change the licensing position of the ProAI Expert website, client content, case studies, or brand assets.

Minimum published rules

• MRG001 expected locale route missing;
• MRG002 HTML language mismatch;
• MRG003 canonical missing or conflicting;
• MRG004 self hreflang missing;
• MRG005 expected alternate missing or wrong;
• MRG006 reciprocal alternate missing;
• MRG007 duplicate or conflicting hreflang values;
• MRG008 alternate target broken, redirected, noindexed, or non-canonical;
• MRG009 x-default missing or inconsistent;
• MRG010 invalid sitemap member;
• MRG011 required canonical route absent from sitemap;
• MRG012 incompatible locale assignment.

Product and discovery gate

• Review current open-source hreflang, sitemap, i18n, and technical-SEO tools.
• Identify the narrow capability gap.
• Define the working name and repository slug.
• Owner approves the product direction.
• Owner approves TypeScript + Node.js 24.
• Owner approves MIT for the standalone tool.
• Owner approves CLI + GitHub Action for v0.1.0.
• Prepare implementation specification and repository file tree.
• Define fixtures and rule-level test matrix.
• Define configuration, CLI, Action, security, privacy, reporting, CI, and release contracts.
• Create the dedicated public repository.
• Apply repository Description, Topics, license, branch, and review settings.
• Create the initial implementation issue backlog.
• Implement the repository foundation and configuration parser.
• Implement and validate all 12 rules.
• Validate CLI on Linux, Windows, and macOS.
• Validate the Action in a clean sample repository.
• Publish v0.1.0 only after the complete release gate passes.

Initial implementation backlog

1. Foundation: repository, TypeScript, CI, license, and action metadata.
2. Configuration: YAML schema, normalization, and validation.
3. Sources: static directory loader and protected HTTP preview loader.
4. Parsing: HTML, canonical, hreflang, robots, and sitemap.
5. Rules: MRG001–MRG006 route and reciprocity checks.
6. Rules: MRG007–MRG012 conflict and sitemap checks.
7. Reports: console, JSON, Markdown, and deterministic ordering.
8. GitHub Action: inputs, annotations, summary, outputs, and failure state.
9. Fixtures: positive and negative controls for every public rule.
10. Release: docs, sample repository, bundle verification, and v0.1.0.

MVP acceptance criteria

• validates an approved correct multilingual fixture without false critical findings;
• detects missing reciprocal alternates;
• detects canonical/alternate conflicts;
• detects sitemap-plus-noindex conflicts;
• detects broken or redirected alternate targets;
• validates explicit locale clusters without guessing translated slugs;
• produces stable Markdown and JSON reports;
• creates useful GitHub workflow annotations;
• fails the workflow according to the configured severity threshold;
• includes positive and negative tests for every published rule;
• includes installation, examples, privacy, security, limitations, contributing, and license documentation;
• publishes a real v0.1.0 release only after representative validation.

Deliberate non-goals

• general SEO scoring;
• keyword, backlink, or ranking analysis;
• Core Web Vitals;
• security or accessibility scanning;
• translation;
• automatic production fixes;
• AI-generated findings;
• Search Console integration;
• unrestricted large-site crawling.

Distribution after release

• controlled fixture demonstration;
• ProAI Expert Insights article;
• LinkedIn engineering and business post;
• X release thread with one reproducible example;
• profile README update only after the repository and release exist.