Improve Najm example against eval audit

[adewale]

Draft stacked PR after #12 and #13.

Because I do not have write access to create stack base branches in Nutlope/hallmark, this PR targets main. Until the parent PRs merge, GitHub's default Files changed view will include parent diffs. The intended child diff is:

adewale/hallmark@pr/tally-eval-audit...pr/najm-eval-audit

What

Improves the Najm example using the eval audit from #12 while preserving the Moroccan fashion/drop direction.

Targeted changes:

• switches body copy away from overused Inter to Source Sans 3 while keeping Bricolage Grotesque for display
• removes glassmorphism from the sticky nav and product tag
• tokenizes raw OKLCH gradients in product/editorial surfaces
• fixes low-contrast accent-filled badges/buttons detected by the audit
• removes emoji/star glyphs used as decorative feature markers
• changes the cart drawer from a modal dialog role to a labelled region, matching its non-focus-trapping drawer behavior
• fixes skipped footer heading levels
• adds root overflow-x: clip
• keeps announcement content visible on mobile instead of hiding it
• removes rote hover-scale transforms
• adds disabled-state coverage

Why

Najm was another low-scoring real example in the audit. This PR is the second proof-of-value pass: the eval harness can identify concrete, fixable issues in existing examples without requiring a wholesale redesign.

Audit evidence

Before this PR:

examples/najm/  v1 3.12  v2 3.27
findings: type-overused-font, color-token-discipline, color-ink-on-ink,
visual-glassmorphism, layout-center-everything, layout-arbitrary-spacing,
layout-skipped-heading, motion-hover-scale, interaction-emoji-icon,
interaction-modal-reflex, responsive-overflow-clip,
responsive-feature-amputation, general-state-coverage

After this PR:

examples/najm/  v1 5.00  v2 5.00
findings: —

Testing

node evals/check.mjs
node evals/audit-site.mjs site/examples/najm/index.html

Observed:

PASS v1: 98.5/100   rules 37   fixtures 3
PASS v2: 98.7/100   rules 43   fixtures 5   structure 5.00/5

examples/najm/  v1 5.00  v2 5.00   —

Risk

This touches a visual example, so browser review is still needed. The largest semantic change is the cart drawer role: the drawer was labelled as modal, but the implementation does not trap focus, so role="region" better matches the current behavior.

[vercel]

@adewale is attempting to deploy a commit to the Together AI Team on Vercel.

A member of the Team first needs to authorize it.

[riju568]

1. The 57+ Gate Slop-Test Checkers

Hallmark uses a strict suite of automated tests (references/slop-test.md) to block typical LLM UI layout "tells." Your PR will not pass if it introduces any code, updates templates, or changes themes and fails the following hard-coded tests:

1. Token Purity (Mid-render improvisations): The gate validation suite needs to see every declaration of a color or font family resolve to a design token (e.g. Var(--color-accent) or font-family: var(--font-display)). Inline hex codes,rgb(), or oklch() strings will cause failures.
   2.Blank Grid Tracks: Within a responsive layout, image-based grid tracks must adopt minmax(0, 1fr) to prohibit the layout overflow on mobile breakpoints rather than the bare 1fr.
2. Bare-grid-tracks Inside any responsive layout, a grid track that contains images and is set with a bare 1fr instead of minmax(0, 1fr) will result in layout overflow when displayed at mobile breakpoint ranges.
3. Rules Of The Road: Hallmark doesn’t allow you to manually hand-make mock browser chrome, phone frames or IDE window chrome.

Multi-Assistant Paths and Frontmatter Errors

It’s Cross Compatible! Hallmark is compatible across Claude Code, Cursor and Codex so you have to change in structurallayout in one and it should make a corresponding change in the other parsing environment!

1. Cursor .mdc Clashes: Upon mapping core rules to the .cursor/rules/hallmark.mdc system, we have an issue with the frontmatter. If a PR touches SKILL.md without taking into consideration what happens when auto generation script rolls into the Cursor/Codex directory rules, we have breakage.
2. Pre-Emit Self-Critique Stamps: If the PR makes new generation outputs, then the output is required to adhere to the 6-axis (Philosophy, Hierarchy, Execution, Specificity, Restraint, Variety) standard and output the required header comment block:

/ Hallmark pre-emit critique: P5 H4 E5 S4 R5 V5 /

Together AI Custom Mode Fallback
Remember that if the PR will be involved in the generation of themes or creative intent filters that we run 20 catalogue themes against the data on each locale, and pull a Together AI API payload together for our custom palette assembly. If you touch the prompt parsing payload and data pipeline for this with your PR it can break our silently fallback to local tokens when the API key is absent.