[yurynix]

Note

Description

base44 publish now declares the app's workflow files alongside its entities and agents, so a recorded version captures the workflows the build produced. The payloads go up raw — keyed the way the platform names the same file — and workflows is always sent, {} for an app with none, because the platform requires the field and refuses a declare without it. Workflows follow the platform's own reading of that directory, which differs from entities and agents in two rules: only .jsonc counts (a .json file there is an ordinary file), and dot-files count (.draft.jsonc is the workflow .draft).

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• core/version/artifacts.ts: collectResources now also reads the workflows directory and returns a workflows map; readRawResources takes options for the extension glob and for including dot-files, so workflows are restricted to CONFIG_FILE_EXTENSION (.jsonc) and read with dot: true, while entities and agents keep {json,jsonc} and skip dot-files. Keys are the file path with the extension stripped, so workflows/daily-digest.jsonc → daily-digest, a hidden .draft.jsonc → .draft, and a nested file keeps its relative path (sub/x).
• core/version/schema.ts: added workflows: Record<string, unknown> to ArtifactSet, documented as always-sent ({} when empty); the actors comment now states the same contract.
• core/version/api.ts: createVersion sends workflows in the declare body.
• core/project/schema.ts: new workflowsDir project-config setting, defaulting to workflows.
• core/project/target.ts: BuildTarget carries workflowsDir (same default), resolved from configDir like the other resource directories.
• docs/versions.md: documented the workflows payload, the .jsonc-only and dot-files rules, the always-sent {} contract, and added the workflows keyword. Corrected the actors note: the platform requires the field on every declare and refuses a declare without it with 422 invalid_request, not only for an app that has actors (409 actors_undeclared).

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

New/updated coverage:

• tests/core/version-artifacts.spec.ts: keying by path (including nested), JSONC parsed and sent raw, .jsonc-only selection, a hidden .draft.jsonc being taken as a workflow, a parse failure naming the file (ConfigInvalidError), and reading from a configured workflowsDir.
• tests/cli/publish.spec.ts: the declare body carries the fixture's workflow and ignores the .json file beside it; an app with no workflows declares workflows: {}.
• tests/core/project-target.spec.ts: workflowsDir in the resolved build target.
• New fixtures under tests/fixtures/publishable/base44/workflows/: daily-digest.jsonc and a notes.json that must be ignored.

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

Behind the existing BASE44_VERSIONS_API gate, like the rest of the versions lane. Workflow payloads are deliberately not read through a validated resource reader — the platform's own extractor and validation are authoritative, matching how entities and agents are already handled. The dot-file rule is scoped to workflows: readRawResources defaults to dot: false, so entity and agent collection is unchanged.

---

_{🤖 Generated by Claude | 2026-11-04 12:54 UTC | 48ac1e4}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.3.1-pr.691.71865f0

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.3.1-pr.691.71865f0"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.3.1-pr.691.71865f0"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.3.1-pr.691.71865f0
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[yurynix]

Do not merge or release yet. apper's DeclareVersionRequest forbids unknown fields, so every publish from this CLI gets a 422 until apper PR 1 (base44/apper#37387, workflows on the declare body) is live in production. This PR stays a draft until then. (The auto-generated description regenerates on each push, so the gate lives here instead.)