chore: upgrade SDK catalog + block structure, fix build errors

[blackcat]

Summary

Upgrades the SDK catalog and applies the block-tools structure upgrade, then fixes the build/type/runtime errors the upgrade surfaced.

Upgrade

• Bump catalog: @platforma-sdk/model & ui-vue → 1.80.10, workflow-tengo → 6.8.2, package-builder → 3.14.2, block-tools → 2.12.9, ts-builder → 1.6.1, plus related tooling.
• Regenerated block structure: new block/src/ facade, removed legacy block/index.{js,d.ts} and workflow/{tsconfig.json,vitest.config.mts}, added mark-stable workflow.

Fixes

• Workflow resources API — migrated the exec resource request from the deprecated .cpu()/.mem()/.gpuMemory() setters to .resources({ onCPU, onGPU }) (adaptive: GPU allocation when the backend has one, CPU fallback otherwise), matching clonotype-space. Also fixes a pre-existing syntax error in the old code.
• vue version — pinned to exact 3.5.24 (was ^3.5.24), so ui and ui-vue resolve a single copy. Fixes TS2345: SdkPluginV2 ... not assignable to Vue Plugin.
• ui-vue/styles — removed the import "@platforma-sdk/ui-vue/styles"; the new ui-vue dropped that export.
• Model export — renamed model → platforma and updated the UI consumer, matching the convention the regenerated block facade expects. Fixes TS2305: has no exported member 'platforma'.

Verification

pnpm run check passes all 8 tasks (type-check, lint, format, build across model/ui/workflow/block/software).

Greptile Summary

Upgrades the Platforma SDK/toolchain and regenerates the block facade while adapting workflow resource allocation and package structure.

• Block facade — the generated ESM facade exports the model contract, inferred data/output types, and packaged-block pointers.
• Platforma model — the block model definition, renamed from model to platforma, describes arguments, UI state, outputs, sections, and GPU report types; consumers now use the new export.
• Resource allocation — the workflow’s execution-resource type changes from separate CPU, memory, and GPU-memory setters to adaptive onCPU and onGPU resource variants.
• GPU software package — the Python artifact definition remains the executable GPU-inspection package, while its post-build NVIDIA environment injection is removed.
• SDK catalog — centralized exact versions for model, UI, workflow, packaging, facade, and TypeScript build tooling are upgraded; Vue is pinned to one exact version.
• CI workflows — pull-request builds now enable tests, and a manually dispatched stable-release workflow is added.
• Private workspace packages — model, UI, workflow, and GPU software packages are marked private because the block package is the publication boundary.

Confidence Score: 3/5

The CI test failure should be fixed before merging; pinning the new release workflow dependencies is also recommended.

Testing is newly enabled, but the model and UI test scripts invoke an executable those workspaces no longer declare, so pull-request and release builds can fail before completion.

Files Needing Attention: .github/workflows/build.yaml, model/package.json, ui/package.json, .github/workflows/mark-stable.yaml

Security Review

The new stable-release workflow references mutable v4 action tags while passing npm and AWS credentials. Pin both references to reviewed commit SHAs. How this was verified: the workflow’s uses entries are tag-based and its secrets block passes publishing credentials to the referenced workflow.

Important Files Changed

Filename	Overview
workflow/src/main.tpl.tengo	Replaces deprecated resource setters with adaptive CPU/GPU allocation and preserves execution outputs.
block/src/index.ts	Adds the generated facade types, model export, and URL-based packaged-block pointer.
software/gpu-info/package.json	Upgrades package tooling and removes the custom NVIDIA-environment post-build hook.
.github/workflows/build.yaml	Enables a test phase that reaches undeclared Vitest commands in the model and UI workspaces.
.github/workflows/mark-stable.yaml	Adds manual stable-release automation, but its privileged dependencies use mutable tags.
pnpm-workspace.yaml	Updates the SDK catalog and pins Vue to an exact shared version.
model/src/index.ts	Renames the exported block-model value to platforma without changing its model contract.
ui/src/app.ts	Updates the UI integration to consume the renamed platforma model export.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Model[Platforma model] --> Facade[Generated block facade]
  Model --> UI[Vue UI]
  UI --> Args[Block arguments]
  Args --> Workflow[Tengo workflow]
  Workflow --> Resources{GPU requested?}
  Resources -->|Yes| Adaptive[onCPU / onGPU allocation]
  Resources -->|No| CPU[onCPU allocation]
  Adaptive --> Software[GPU-info Python package]
  CPU --> Software
  Software --> Report[GPU report and logs]
  Facade --> Pack[Published block pack]

Loading

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
.github/workflows/build.yaml:30
**Workspace test executables are missing**

When CI runs the newly enabled test phase, the root script delegates to `turbo run test`, which executes the retained `test: vitest` scripts in the model and UI workspaces even though this change removes their Vitest dependencies, causing the build workflow to terminate with `vitest: command not found`.

### Issue 2 of 2
.github/workflows/mark-stable.yaml:8
**Release actions use mutable tags**

The new stable-release workflow loads both its initialization action and publishing workflow through mutable `v4` tags while passing npm and AWS credentials, allowing a moved upstream tag to run unreviewed code with release credentials. Pin both references to reviewed commit SHAs. **How this was verified:** the workflow uses tag-based `uses` references and passes publishing credentials to the referenced workflow.

_{Reviews (1): Last reviewed commit: "chore: upgrade SDK catalog + block struc..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

Context used:

• Context used - Terms is a types in codebase. Provide the list of ... (source)

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[greptile-apps]

Workspace test executables are missing

When CI runs the newly enabled test phase, the root script delegates to turbo run test, which executes the retained test: vitest scripts in the model and UI workspaces even though this change removes their Vitest dependencies, causing the build workflow to terminate with vitest: command not found.

Prompt To Fix With AI

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

Comment:
**Workspace test executables are missing**

When CI runs the newly enabled test phase, the root script delegates to `turbo run test`, which executes the retained `test: vitest` scripts in the model and UI workspaces even though this change removes their Vitest dependencies, causing the build workflow to terminate with `vitest: command not found`.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Release actions use mutable tags

The new stable-release workflow loads both its initialization action and publishing workflow through mutable v4 tags while passing npm and AWS credentials, allowing a moved upstream tag to run unreviewed code with release credentials. Pin both references to reviewed commit SHAs. How this was verified: the workflow uses tag-based uses references and passes publishing credentials to the referenced workflow.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/mark-stable.yaml
Line: 8

Comment:
**Release actions use mutable tags**

The new stable-release workflow loads both its initialization action and publishing workflow through mutable `v4` tags while passing npm and AWS credentials, allowing a moved upstream tag to run unreviewed code with release credentials. Pin both references to reviewed commit SHAs. **How this was verified:** the workflow uses tag-based `uses` references and passes publishing credentials to the referenced workflow.

How can I resolve this? If you propose a fix, please make it concise.

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!