fix: align plugin service names with CoreServiceName enum from @objectstack/spec

[Copilot]

Three plugins register services with names that don't match the CoreServiceName enum defined in @objectstack/spec. The protocol specifies 17 canonical service names; these three were out of sync.

Changes

Package	Before	After
@objectos/realtime	'websocket-server'	'realtime'
@objectos/storage	'storage'	'file-storage'
@objectos/jobs	'jobs'	'job'

Updated in each package:

• registerService() call in init()
• getService() call in exported get*API() helper
• Health check checks[].name
• Log messages
• All test assertions

// Before
ctx.registerService('websocket-server', { ... });

// After — matches CoreServiceName enum
ctx.registerService('realtime', { ... });

Reference: https://protocol.objectstack.ai/docs/guides/kernel-services

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectos	Error		Feb 9, 2026 2:17pm

[hotlong]

@copilot 本项目的 service还有 workflow
automation

[Copilot]

Pull request overview

This PR updates several kernel plugin service registration names to match the canonical CoreServiceName enum from @objectstack/spec, ensuring runtime service discovery aligns with the protocol.

Changes:

• Renamed registered service names for @objectos/realtime, @objectos/storage, and @objectos/jobs to realtime, file-storage, and job.
• Updated corresponding get*API() helpers and test assertions to use the new service names.
• Regenerated pnpm-lock.yaml reflecting dependency/metadata updates.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Lockfile updated (includes broader dependency/metadata changes beyond service-name renames).
packages/storage/src/plugin.ts	Registers storage service under file-storage; updates getStorageAPI() accordingly.
packages/storage/test/plugin.test.ts	Updates service registration assertion to file-storage.
packages/realtime/src/plugin.ts	Registers realtime service under realtime; updates log + health check check name.
packages/realtime/test/plugin.test.ts	Updates service map key and assertions to realtime.
packages/jobs/src/plugin.ts	Registers jobs service under job; updates getJobsAPI() accordingly.
packages/jobs/test/plugin.test.ts	Updates service registration assertion to job.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

The test case description still refers to the old service name ("websocket-server"), even though the assertions now use "realtime". Updating the it(...) string will keep test output and intent aligned with the new CoreServiceName.

[Copilot]

pnpm-lock.yaml changes include dependency scope updates beyond the 3 plugin service-name renames (e.g. adding @objectstack/spec to additional importers like packages/cache). Please confirm these extra dependency changes are intentional and reflect them in the PR description (or split them into a separate PR to keep review scope focused).

[Copilot]

This lockfile update adds widespread metadata fields (e.g. libc: [...] on many platform-specific packages), which typically means it was regenerated with a different pnpm version/config. If this PR’s intent is only service-name alignment, consider regenerating with the repo-standard pnpm setup (or isolating lockfile-format changes) to reduce unrelated churn and merge conflicts.

Suggested change

	libc: [glibc]
	'@img/sharp-libvips-linux-arm@1.2.4':
	resolution: {integrity: sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A==}
	cpu: [arm]
	os: [linux]
	libc: [glibc]
	'@img/sharp-libvips-linux-ppc64@1.2.4':
	resolution: {integrity: sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA==}
	cpu: [ppc64]
	os: [linux]
	libc: [glibc]
	'@img/sharp-libvips-linux-riscv64@1.2.4':
	resolution: {integrity: sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA==}
	cpu: [riscv64]
	os: [linux]
	libc: [glibc]
	'@img/sharp-libvips-linux-arm@1.2.4':
	resolution: {integrity: sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A==}
	cpu: [arm]
	os: [linux]
	'@img/sharp-libvips-linux-ppc64@1.2.4':
	resolution: {integrity: sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA==}
	cpu: [ppc64]
	os: [linux]
	'@img/sharp-libvips-linux-riscv64@1.2.4':
	resolution: {integrity: sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA==}
	cpu: [riscv64]
	os: [linux]

[Copilot]

@copilot 本项目的 service还有 workflow
automation

workflow and automation already register with the correct CoreServiceName values — context.registerService('workflow', this) at packages/workflow/src/plugin.ts:81 and context.registerService('automation', this) at packages/automation/src/plugin.ts:90. These match the spec enum exactly, so no changes were needed for them.