rcf-lite 0.22.0 → 0.23.0

package/releases/releases.yaml

@@ -40,8 +40,18 @@
 # `npm install rcf-lite`.
 
 feedVersion: 1
-latest: "0.22.0"
+latest: "0.23.0"
 releases:
+  - version: "0.23.0"
+    date: "2026-09-07"
+    breaking: false
+    headlines:
+      - "rcf-lite 0.23.0 adds the infrastructure spine four blueprints wide: a Postgres store with a facade contract and forward-only migrations, an S3-shape object store with a Cloudflare R2 first adapter, a Cloudflare Queues producer and consumer with dead-letter semantics, and a background-jobs discipline that refuses to apply until a queue is applied."
+      - "Each blueprint verifies against the real engine with node-only probes, and the four surfaces compose through the capability mechanism the round-3 admin console shipped."
+      - "Also in this release: the deploy-cloudflare-workers blueprint bumps 1.1.0 to 1.2.0 to bless the Workers-with-static-assets shape as the SPA-on-Workers deploy shape, and a CLI stdout-flush fix so large outputs are not truncated at the pipe buffer."
+    minAgentAction: null
+    notesUrl: "https://stravica.ai/docs/rcf/changelog/"
+
   - version: "0.22.0"
     date: "2026-09-07"
     breaking: false

package/src/blueprint/apply.js

@@ -397,10 +397,13 @@ export async function applyBlueprint({ projectRoot, tree, source, displaySource,
             const flag = blueprint.requiresAppliedCapabilities?.allowSkipFlag ?? 'allow-no-auth-yet';
             const caps = (blueprint.requiresAppliedCapabilities?.capabilities ?? []).join(', ');
             // Predecessor-family prose is derived from the flag name so
-            // the note reads sensibly for both the auth override ("auth
-            // blueprint") and the secrets override ("secrets-management
-            // blueprint") without the runner learning the family list.
-            const family = flag.includes('secrets') ? 'secrets-management' : 'auth';
+            // the note reads sensibly for the auth override, the secrets
+            // override, and the queue override (infra round 5 T-4)
+            // without the runner learning the family list. New families
+            // extend by pattern-matching a substring of the flag name.
+            const family = flag.includes('secrets')
+              ? 'secrets-management'
+              : (flag.includes('queue') ? 'queue' : 'auth');
             return `no ${family} yet: applied under --${flag}; surfaces gated on ${caps} will refuse at runtime until a ${family} blueprint is applied.`;
           })()
         : undefined,

package/src/blueprint/capabilities.js

@@ -129,6 +129,31 @@ export function buildRefusalMessage({ slug, refusalMessageId, requiredCapabiliti
       `       rcf define blueprint add ${slug} --${allowSkipFlag}`,
     ].join('\n');
   }
+  if (refusalMessageId === 'jobs-background-no-queue') {
+    // Infra round 5 T-4 (spec 5.4, Baz decision 5). Names the shipped
+    // queue provider explicitly (messaging-queue-cloudflare v1.0.0) so
+    // an operator hitting the refusal has the shipped answer in hand
+    // without a shelf-wide grep. Q3 default per spec section 10: the
+    // refusal asserts both exit code AND stable message id.
+    return [
+      `[jobs-background-no-queue] ${slug} requires an applied blueprint declaring`,
+      `at least one of: ${requiredCapabilities.join(', ')}`,
+      `or an operator override with --${allowSkipFlag}.`,
+      `The shipped provider is messaging-queue-cloudflare (v1.0.0+); a future`,
+      `messaging-queue-postgres sibling (Baz decision 7) will provide the same`,
+      `capability when demand mints it.`,
+      '',
+      'Applied blueprints on this project:',
+      appliedBlock,
+      '',
+      'Suggested next steps:',
+      '  1. Apply messaging-queue-cloudflare first:',
+      '       rcf define blueprint add messaging-queue-cloudflare',
+      `  2. Or override for a scaffolding pass (records a note on the applied`,
+      `     sidecar so later validation flags the surface as not-yet-activated):`,
+      `       rcf define blueprint add ${slug} --${allowSkipFlag}`,
+    ].join('\n');
+  }
   if (refusalMessageId === 'object-storage-s3-no-secrets') {
     return [
       `[object-storage-s3-no-secrets] ${slug} requires an applied blueprint declaring`,

package/src/cli/blueprint.js

@@ -196,6 +196,12 @@ const OPTION_SPEC = {
   // with the credential-pair discipline the spec names, rather than
   // reusing the auth-flavoured flag.
   'allow-no-secrets-yet': { type: 'boolean' },
+  // Infra round 5 T-4 (spec 5.4, Baz decision 5): jobs-background
+  // declares allowSkipFlag "allow-no-queue-yet" so the override for
+  // its requiresAppliedCapabilities gate stays semantically aligned
+  // with the queue-capability discipline the spec names, rather than
+  // reusing the auth or secrets flavoured flags.
+  'allow-no-queue-yet': { type: 'boolean' },
   answer: { type: 'string', multiple: true },
   answers: { type: 'string' },
 };
@@ -346,7 +352,8 @@ export async function main(argv, deps = {}) {
       projectRoot, tree, source,
       namespaceOverride: parsed.values.namespace,
       allowNoAuthYet: parsed.values['allow-no-auth-yet'] === true
-        || parsed.values['allow-no-secrets-yet'] === true,
+        || parsed.values['allow-no-secrets-yet'] === true
+        || parsed.values['allow-no-queue-yet'] === true,
       elicitAnswers,
       customAuthReadLine,
       // Library-qualified resolves rewire the applied identity under