Skip to content

module-kit 0.4.1: a runtime stating production never writes without LAZURIO_RUNTIME_DATA_WRITER=true - #10

Merged
immakermatty merged 1 commit into
mainfrom
agent/datawriter-production
Nov 18, 2026
Merged

immakermatty merged 1 commit into
mainfrom
agent/datawriter-production

Conversation

@immakermatty

Copy link
Copy Markdown
Contributor

Status: ready for review

Fixes #9. dataWriter(access, env) returned true for a local or environment entry whenever LAZURIO_RUNTIME_DATA_WRITER was missing, also in a runtime that states LAZURIO_RUNTIME_DEPLOYMENT=production. That contradicts the Module Standard's writer rule (a production runtime never writes without true).

Change

  • dataWriter (src/tools.ts): when the writer variable is set it still decides. Without it, LAZURIO_RUNTIME_DEPLOYMENT=production returns false for every entry. Otherwise (a development version) only a local or environment entry writes, as before.
  • Version and README: package.json is 0.4.1. The README states the rule. The install line stays on the released v0.4.0 until the tag exists.

Impact (checked in #9)

No deployed Application is affected. Clients v0.7.1 and Revize v0.2.0 use dataWriter and both declare data, so the host sets the writer variable (true and false). The others are on v0.3.0. The host doesn't yet state LAZURIO_RUNTIME_DEPLOYMENT; that's HumanAndMachine-ai/Machines#1386 and Lazurio/LazurioPlatform#1041. Until then this rule takes effect only where a runtime states it.

Verification

  • New tests:
    • production without the variable gives false for each entry (local, environment, app admin and user, unknown);
    • with the variable, true and false still decide;
    • a development version (no deployment, or environment) keeps local and Environment writes;
    • in such a runtime a registry lists no write tool to a local entry.
  • bun run check passes and bun test gives 113 pass, 0 fail.

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:3e1c89fb-5ac2-43b2-9ec4-23f4a2e51382

🤖 Generated with Claude Code

…AZURIO_RUNTIME_DATA_WRITER=true

dataWriter returned true for a local or Environment entry whenever the writer
variable was missing, also in a runtime that states
LAZURIO_RUNTIME_DEPLOYMENT=production, against the Module Standard's writer
rule (#9). It now refuses there; the writer variable still decides where it
is set, and a development version keeps its local and Environment writes.
Tests for every entry and for a registry's list. No deployed Application is
affected (checked in #9).

Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:3e1c89fb-5ac2-43b2-9ec4-23f4a2e51382

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@agentrozjedemeai agentrozjedemeai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Schvaluji. Blokující nálezy nemám.

Ověření: TypeScript kontrola a 113 testů prošly lokálně; Python kontroly prošly v CI. Lokálně Python kontroly nešly spustit, protože zde není uv.

Order and migrations: Ochrana platí až tam, kde runtime uvádí production; pro všechny produkční aplikace je třeba dokončit https://github.com/HumanAndMachine-ai/Machines/issues/1386 a související Lazurio/LazurioPlatform#1041.

— Pablo

@immakermatty
immakermatty merged commit 063372c into main Nov 18, 2026
3 checks passed
@immakermatty
immakermatty deleted the agent/datawriter-production branch November 18, 2026 03:40
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.

dataWriter lets a local or Environment entry write in a runtime stating production

2 participants