@odla-ai/cli 0.42.0 → 0.42.1

package/dist/bin.js

@@ -174,7 +174,7 @@ function absoluteEntryPath(entryPath) {
 
 // src/bin.ts
 var argv = process.argv.slice(2);
-requireCurrentCliForProvision(argv).then(() => requireCoherentProvisionRuntime(argv)).then(async () => (await import("./cli-EGZGMIKB.js")).runCli()).catch((err) => {
+requireCurrentCliForProvision(argv).then(() => requireCoherentProvisionRuntime(argv)).then(async () => (await import("./cli-K5SBFFAY.js")).runCli()).catch((err) => {
   console.error(redactSecrets(`odla-ai: ${err instanceof Error ? err.message : String(err)}`));
   process.exitCode = exitCodeFor(err);
 });

package/dist/{chunk-74DXL2MT.js → chunk-FWPQSTNF.js}

@@ -10730,12 +10730,10 @@ Commands:
                explicitly. Same device-grant auth as "app".
                Status changes and comments post to each item's @odla-ai/chat
                discussion thread.
-               NOTE: "--column ready" is OWNER-ONLY. Creating a task in Ready
-               approves its complete execution contract, so it needs pm.plan,
-               which no device enrollment or handshake approval can grant. An
-               agent proposes in Backlog (the default); a human owner or a
-               pm.plan agent promotes. This is deliberate, not a permission
-               gap \u2014 it was reported as one.
+               Creating or promoting a task in Ready requires a complete
+               execution contract and a reviewed revision. Any caller with PM
+               mutation access to that app/project may do it; claims coordinate
+               execution but never own or lock the PM record.
   bug          Intent-first alias for PM bugs. "bug report" writes to
                odla PM; odla product defects do not belong in GitHub Issues.
   discuss      Group discussions (via @odla-ai/chat) for the apps you co-own:
@@ -15811,4 +15809,4 @@ export {
   isTerminalHostedSecurityStatus,
   runCli
 };
-//# sourceMappingURL=chunk-74DXL2MT.js.map
+//# sourceMappingURL=chunk-FWPQSTNF.js.map