Show only block results in the UI table

[mzueva]

• Fix result UI table to show scores only from current block
• Migrate to the latest block layout

Greptile Summary

The PR scopes the results table to score columns produced by the current block and migrates the package to the latest block-kind layout and SDK toolchain.

• Adds a typed block-kind package and round-trip template initialization parameters.
• Supplies the current workflow’s score columns directly to the table while excluding discoverable FACS-bin scores from other block instances.
• Upgrades Platforma SDK packages and CI to Node.js 22, adjusts publication configuration, and disables the block workflow’s test stage.
• Important touched terms:
  • Block kind — the typed identity and initialization contract for a Platforma block; newly introduced through kind/ and connected to the data model.
  • BlockParams — optional initialization values used when creating a block from a template; newly defines metadata column references, gate ordering, and selection snapshots.
  • Template parameters — configuration exported from one block and supplied when creating another; the model now projects the seven BlockParams fields through templateParams.
  • PColumn — a typed Platforma data column identified by its name, axes, domain, and annotations; current-run score PColumns now become primary table columns.
  • Primary table columns — authoritative columns supplied directly to the table rather than discovered from the project pool; now sourced from this block’s scoresPf output.
  • Result-pool discovery — lookup of related project columns sharing the result axis; now excludes the complete pl7.app/facsBin/ namespace to prevent sibling-block scores from appearing.
  • Gate rank mean — the read-weighted mean gate position for a variant and condition; remains the table anchor and is now shown only from the current block.
  • Bin score — the parent-relative difference in gate steps; remains conditionally available and is now scoped to the current block.

Confidence Score: 4/5

The PR appears safe to merge, but restoring the package test stage would preserve non-blocking release verification for the assembled block.

The current-block table scoping and block-kind migration are internally consistent, while the only accepted concern is that the main block CI lane no longer executes its configured integration tests.

Files Needing Attention: .github/workflows/build.yaml

Important Files Changed

Filename	Overview
kind/src/index.ts	Introduces the block identity, typed initialization parameters, and runtime validation for template-supplied values.
model/src/dataModel.ts	Connects the block kind to the existing model version and seeds new instances from optional template parameters.
model/src/index.ts	Scopes score columns to the current workflow output, filters score discovery, and adds template-parameter export.
.github/workflows/build.yaml	Moves CI to Node.js 22 but disables the package test stage, removing assembled-block test coverage from this lane.
block/package.json	Adds the block-kind workspace dependency and changes the block-tools publication invocation.
pnpm-workspace.yaml	Registers the new kind package and upgrades the shared Platforma SDK and build-tool catalogs.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  T[Template parameters] --> K[Block kind parser]
  K --> D[Initialized block data]
  D --> W[Workflow run]
  W --> S[Current scoresPf]
  S --> P[Primary score columns]
  R[Project result pool] --> X[Exclude pl7.app/facsBin namespace]
  X --> C[Related variant columns]
  P --> V[Results table]
  C --> V

Loading

Prompt To Fix All With AI

### Issue 1
.github/workflows/build.yaml:33
**Package tests are disabled**

Setting `test: false` prevents the reusable block workflow from invoking the configured repository test script, removing package-level verification of the assembled workflow, model, UI, and analysis package before publication.

```suggestion
      test: true
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Fix changeset level" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used (5)

• Knowledge Base — Platforma integration contract
• Knowledge Base — Analysis data model
• Knowledge Base — Platforma block integration
• Knowledge Base — CI build and stability
• Knowledge Base — Verification and release

[greptile-apps]

Package tests are disabled

Setting test: false prevents the reusable block workflow from invoking the configured repository test script, removing package-level verification of the assembled workflow, model, UI, and analysis package before publication.

Suggested change

	test: false
	test: true

Knowledge Base Used:

• CI build and stability
• Verification and release

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/build.yaml
Line: 33

Comment:
**Package tests are disabled**

Setting `test: false` prevents the reusable block workflow from invoking the configured repository test script, removing package-level verification of the assembled workflow, model, UI, and analysis package before publication.

```suggestion
      test: true
```

**Knowledge Base Used:**
- [CI build and stability](https://app.greptile.com/milaboratories/-/custom-context/knowledge-base/platforma-open/sort-seq-analysis/-/docs/ci-build-and-stability.md)
- [Verification and release](https://app.greptile.com/milaboratories/-/custom-context/knowledge-base/platforma-open/sort-seq-analysis/-/docs/verification-and-release.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!