Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/ComparisonFAQ.astro`:
- Around line 27-30: Update the FAQ entry in ComparisonFAQ.astro that has
question "What license is SynthOrg under and what does it mean?" so it correctly
states the conversion mechanism and current change date: replace the hardcoded
line "converts to Apache 2.0 on February 27, 2030" with text explaining that
each released version converts to Apache 2.0 automatically three years after its
individual release, and note the current version's Change Date is April 2, 2029
(as in LICENSE); keep examples for small orgs but remove the single fixed
conversion date claim so future releases can have different conversion dates.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@site/src/components/islands/ComparisonTable.css`:
- Around line 255-258: The ct-scroll-pulse keyframes continue animating for
users who prefer reduced motion; add a prefers-reduced-motion override that
disables or neutralizes this animation: create an `@media`
(prefers-reduced-motion: reduce) block that either sets animation: none (or
animation-name: none) on the selectors that use ct-scroll-pulse and/or redefines
`@keyframes` ct-scroll-pulse to a no-op, and apply the same change for the other
ct-scroll-pulse occurrences noted (lines ~630-634) so the pulse stops when
reduced motion is requested.

In `@site/src/components/islands/ComparisonTable.tsx`:
- Around line 415-432: Add an Escape key handler so users can exit full-width
mode with the keyboard: when the fullWidth state is true (in the ComparisonTable
component) register a keydown listener (e.g., in a useEffect) that calls
setFullWidth(false) when event.key === "Escape", and remove the listener when
fullWidth becomes false or the component unmounts; ensure the listener is
added/removed only while fullWidth is true to avoid leaking handlers or
interfering with other keyboard shortcuts.
- Around line 392-413: The column picker never closes on outside clicks; add a
ref (e.g., pickerRef) to the ct-column-picker container inside the
ComparisonTable component and register a document mousedown/touchstart handler
in a useEffect that calls setShowColumnPicker(false) when the event target is
not contained in pickerRef.current (and optionally when Escape is pressed), and
remove the listener on cleanup; update the JSX to attach the ref to the div with
className "ct-column-picker" so clicks outside properly close the picker.

---

Outside diff comments:
In `@site/src/components/islands/ComparisonTable.tsx`:
- Around line 165-194: The current filtering (inside useMemo computing filtered
in ComparisonTable) intentionally bypasses all filters for items with
c.is_synthorg, which can confuse users; leave the filter behavior as-is but add
a clear visual indicator (badge and hover tooltip) when rendering rows/items
from the filtered array where c.is_synthorg is true so users know "SynthOrg is
always shown for comparison"; update the rendering of the filtered list to check
c.is_synthorg and attach an accessible badge/tooltip explaining the exception.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@data/competitors.yaml`:
- Around line 696-720: The YAML entries for "Inngest AgentKit", "ControlFlow",
and "Motia" are placed under incorrect human-readable section comments; reorder
each entry to sit under the comment that matches its category value (e.g., move
the "Inngest AgentKit" block so it appears within the Multi Agent Framework
section and move "ControlFlow" and "Motia" into the Workflow Engine section) or
remove/update the surrounding section comment headers so they reflect the actual
items; locate entries by their name fields ("Inngest AgentKit", "ControlFlow",
"Motia") and their category: values to perform the adjustment.

---

Outside diff comments:
In `@site/src/components/islands/ComparisonTable.tsx`:
- Around line 685-700: The mobile card rendering currently maps over dimensions
unconditionally (in the block using dimensions.map and SupportIcon) which causes
hidden columns to still appear on mobile; update that mapping to filter
dimensions by the same visibleDimensions set used by the desktop table (e.g.,
replace dimensions.map(...) with dimensions.filter(d =>
visibleDimensions.has(d.key) || visibleDimensions.includes(d.key)).map(...)) so
the mobile card view respects column visibility (ensure you reference the
existing visibleDimensions variable/prop and keep SupportIcon, comp.features and
feat?.note usage intact).
- Around line 20-22: Remove the unused "planned" support value everywhere:
update the FeatureEntry.support type to only "full" | "partial" | "none"; remove
"planned" from SUPPORT_ORDER, SUPPORT_ICONS, and SUPPORT_LABELS constants (and
any associated icon or label entries); and remove the "Planned" item from the
legend rendering in ComparisonTable so it no longer references the removed
value. Ensure any code that iterates or indexes into these constants (e.g.,
where SUPPORT_ORDER is used) is still valid after the removal.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@data/competitors.yaml`:
- Around line 106-119: Inline YAML mappings (e.g., org_structure, multi_agent,
task_delegation, memory, tool_use, human_in_loop, budget_tracking,
security_model, observability, web_dashboard, cli, production_ready,
workflow_types, template_system) use extra spaces immediately inside braces and
violate the `braces` lint rule; fix by normalizing each inline mapping to remove
the space after "{" and before "}" (and keep consistent spacing after commas),
e.g. change "{ support: full, note: ... }" to "{support: full, note: ...}" for
every occurrence in the file.

In `@scripts/generate_comparison.py`:
- Around line 226-230: The code currently masks missing/invalid pricing and
self_hosted fields by defaulting to empty strings; update the validation in the
block that reads pricing_raw = comp.get("pricing", "") and self_hosted_raw =
comp.get("self_hosted", "") so it fails fast: require these keys exist (do not
default to ""), verify the values are members of PRICING_LABELS and
SELF_HOSTED_LABELS respectively, and raise a clear exception (e.g., ValueError)
with the competitor identifier when missing or when the value is not an allowed
enum; keep using PRICING_LABELS.get(...) / SELF_HOSTED_LABELS.get(...) only
after validation so the code doesn’t silently accept invalid inputs.

---

Outside diff comments:
In `@data/competitors.yaml`:
- Around line 72-86: The YAML header is inconsistent with the PR target: update
the categories block and summary count so the file matches the intended 54
entries across 7 categories; specifically add the two missing category entries
(e.g., keys "research" and "protocols" with appropriate labels) into the
categories list and update the comment line "# Competitors (47 entries across 5
categories)" to reflect the correct count and category number (e.g., "#
Competitors (54 entries across 7 categories)"), or alternatively if the PR
intends 47/5 then remove the extra PR targets — ensure the top-level
"categories" list and the summary comment are reconciled with the actual number
of competitor entries in the file.

---

Duplicate comments:
In `@data/competitors.yaml`:
- Around line 697-705: The YAML file has entries whose human-readable section
headers do not match their category fields (e.g., the entries "Inngest
AgentKit", "ControlFlow", and "Motia"); update the document so each entry
appears under the correct section header that corresponds to its category value
(or change the entry's category to match the current section if that was
intended). Locate the entries by the name fields "Inngest AgentKit",
"ControlFlow", and "Motia" and either move those blocks into the section
matching their category (e.g., multi_agent_framework, etc.) or rename the
surrounding section headers to reflect the category values, ensuring consistency
and keeping YAML indentation and ordering intact.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@data/competitors.yaml`:
- Around line 12-23: The reviewers note that typos in pricing/self_hosted
silently pass through because scripts/generate_comparison.py uses .get(key,
default); update _validate_competitors in scripts/generate_comparison.py to
explicitly validate each competitor entry's pricing and self_hosted fields
against the allowed sets (pricing =
{"free","free-restrictive","depends","open-core","paid"} and self_hosted =
{"true","false","partial"}), and raise/throw a clear error (or log and abort
generation) identifying the competitor name and invalid value when a mismatch is
found so generation fails loudly instead of rendering corrupted labels.

In `@site/src/components/islands/ComparisonTable.tsx`:
- Around line 254-256: The file defines two equivalent booleans (hasActiveFilter
and hasFilters); consolidate them into a single variable (pick one name, e.g.,
hasFilters) and remove the duplicate. Update all usages that check for active
filters—specifically the SynthOrg "pinned" badge code that references
hasActiveFilter and the "Clear" button logic that references hasFilters—to use
the single variable, ensuring the condition includes the same operands
(categoryFilter || licenseFilter || featureFilter || search.trim()). Keep the
variable's computation in the same scope as the existing declarations so both UI
branches can reference it.

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@scripts/generate_comparison.py`:
- Around line 112-134: In _validate_competitors, avoid computing name twice by
assigning name = comp.get("name", f"<index {i}>") once immediately after
verifying comp is a mapping, then use that name variable in the missing-keys
error and subsequent validation messages (replace the later name = ... and any
other duplicate lookups), leaving the rest of the logic unchanged.