Skip to content

DEV-1719 Correct action results, caller checks and scheduling references - #321

Open
tonytlwu wants to merge 10 commits into
masterfrom
codex/dev-1719-integration-journey
Open

tonytlwu wants to merge 10 commits into
masterfrom
codex/dev-1719-integration-journey

Conversation

@tonytlwu

@tonytlwu tonytlwu commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Product areas affected

AI-consumed App Actions, Session and Vue routing/bootstrap references, plus their derived full index.

What does this PR do?

Corrects server result envelopes versus direct client values, falsy results/resolved failures, fresh caller checks, dependency loading and Vue routing that could retain a denial after login. Caller identity and provider credentials remain separate concerns.

Documents current scheduling: an active editable action with a frequency can run before publication; editable and published copies need separate attention, and unpublishing alone does not stop the editable action. Deferred whole-project publication promises are excluded. Master's Actions.request() guidance is preserved. No executable, dependency, package version or worker changes.

Verification

  • Candidate 67700d8e22044150b56488d08057a45dfe8ba285, merged master 6359e14f532c6d830674aa3e1603f1c37aae6591; one conflict preserves current transport guidance.
  • 220 unit tests, strict validation of 210 docs / 46 libraries, Jekyll render, exact raw/index comparisons and 11 current-contract checks passed. Exact-head GitHub/Cloudflare checks passed; automated review completed without findings.
  • 18 real Vue/Router JSDOM outcomes retain unchanged source. Native file execution remains unverified; six existing Liquid warnings remain. Documentation rendering does not establish provider acceptance.

JIRA ticket

DEV-1719

Release boundary

Evidence pack records exact sources, tests, production scheduling impact, release order, rollback and remaining acceptance.

This partial release excludes published-only scheduling and new whole-project publication controls. Read-only production evidence found 54 active editable-action schedules; 17 actions ran scheduled in the preceding 30 days without an active published counterpart. Existing jobs are preserved; no customer migration or automatic publication is included. Full work remains recoverable on the preserved follow-up refs/commit ancestry.

This does not complete DEV-1719. Remaining caller/provider outcomes require Arpan's deployed DEV-2338 / runner PR59, then real permitted/denied caller and provider checks. No duplicate runner workaround is included.

Checklist

  • Unit, strict documentation, render and source/index checks.
  • Independent contract review and exact-head CI.
  • Normal human QA/release approvals (two under the HIGH-risk deployment policy).

Deployment instructions

Coordinate API8810 and Studio9049. Publish these current-runtime references before or with Studio; do not publish the preserved full-scope follow-up. No production merge/public-doc deployment is authorized; scheduled follow-ups remain paused.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Deploying fliplet-cli with  Cloudflare Pages  Cloudflare Pages

Latest commit: 67700d8
Status: ✅  Deploy successful!
Preview URL: https://799c78d9.fliplet-cli.pages.dev
Branch Preview URL: https://codex-dev-1719-integration-j.fliplet-cli.pages.dev

View logs

@tonytlwu tonytlwu changed the title DEV-1719: Correct action result and caller authorization documentation DEV-1719 Correct action results, caller checks and scheduling references Oct 19, 2026
@tonytlwu
tonytlwu marked this pull request as ready for review October 20, 2026 00:11
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-20T00:13:49.800300Z 67700d8 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

This branch has not been deployed

No deployments
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.

1 participant