Skip to content

Refresh Foundry instance comparison - #57

Draft
jmchilton wants to merge 1 commit into
mainfrom
codex/refresh-instance-comparison
Draft

Refresh Foundry instance comparison#57
jmchilton wants to merge 1 commit into
mainfrom
codex/refresh-instance-comparison

Conversation

@jmchilton

Copy link
Copy Markdown
Member

Summary

  • remove chronological instance-number metadata and badges from the Instances section
  • replace the stale two-instance Diff with a concise, current three-Foundry comparison
  • update supporting pages to reflect Statistical Genomics' implemented cast skills and the distinction between current critique and future empirical calibration
  • add a regression test that prevents instance numbering from returning

Why

The instance numbers implied a hierarchy that no longer matches how the Foundries evolve. TDA is the current architecture-hardening reference even though it was built after the other profiles.

The old Diff centered only two implementations and had become inaccurate about Statistical Genomics' caster and Galaxy's validation path. The rewrite compares what actually transfers across all three without promoting domain-specific choices into shared substrate.

Impact

The Instances page now presents Foundries by role and current display order rather than ordinal identity. The Diff is substantially shorter and compares all three implementations across evidence, delivery, and checks while clearly identifying unfinished work.

The comparison table is keyboard-focusable and horizontally scrollable on narrow screens.

Validation

  • npm test — 23 tests passed
  • npm run typecheck — 0 errors; one pre-existing unused-index hint
  • npm run build — 23 wiki-link targets resolved, 30 pages built, 30 pages indexed
  • inspected emitted HTML/CSS for the three-Foundry table, responsive overflow, instance-card labels, and removal of instance-number text
  • screenshot QA was unavailable because this session exposed no browser backend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant