feat(agentic): add Agentic runtime app#870
Open
lumberman wants to merge 9 commits into
Open
Conversation
|
🚅 Deployed to the forge-pr-870 environment in forge
|
Collaborator
Author
|
Follow-up validation for the Mastra docs/setup audit: Summary
Red/Green TDD
Validation
User SmokeBuilt Mastra ran on
Screenshots captured locally:
|
Collaborator
Author
|
Renamed the app boundary from Mastra to Agentic per product/deploy naming preference. What changed
Mastra remains only as the underlying framework/Studio/runtime implementation name, including the required Validation
Runtime smokeBuilt app started from
|
…app' into feat/115-mastra-agentic-runtime-app
lumberman
added a commit
that referenced
this pull request
May 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/agenticas@forge/agentic, with Mastra runtime, Studio, auth-gated service/operator boundaries, LibSQL runtime storage config, package-local docs, and Railway config for the futureagenticservice.origin/main, hardened production env validation, enforced distinct service/operator/Manager tokens, made dry-run idempotency durable, preserved Manager semantic errors, and added Agentic callback timeouts.Red/Green TDD
Validation
pnpm --filter @forge/agentic testpnpm --filter @forge/agentic typecheckpnpm --filter @forge/agentic lintpnpm --filter @forge/agentic buildpnpm --filter @forge/manager test -- src/app/api/automations src/features/agents src/lib/agentic-automation-dry-run.test.ts src/config/env.test.tspnpm --filter @forge/manager typecheckpnpm --filter @forge/manager lintpnpm --filter @forge/graphql typecheckpnpm --filter @forge/cms typecheckpnpm turbo run generate --filter=@forge/graphqlpnpm run format:checkgit diff --checkUser Smoke Test
http://127.0.0.1:4114with a fake Manager service athttp://127.0.0.1:3999.GET /healthreturned HTTP 200.GET /returned HTTP 401.GET /returned HTTP 401.GET /returned HTTP 200 and rendered the Studio shell.POST /forge/manager-automation-dry-runreturned success with a Manager run id.not_foundandinvalid_automationfailures were preserved in the Agentic response; invalid Manager JSON returnedmanager_unavailable./tmp/forge-agentic-smoke/operator-studio.png.Post-Deploy Monitoring & Validation
agentic, and the service Config-as-code Path must resolve toapps/agentic/railway.toml; treat a missing/null deploymentconfigFileas a failed live verification.GET /healthreturns HTTP 200 without auth./forge/manager-automation-dry-runrejects anonymous/operator tokens and accepts only the service token.agentic,manager-automation-dry-run,manager_unavailable,run_in_progress,dry_run_failed, token validation errors, storage errors, callback timeouts, and duplicate idempotency records during the first 30 minutes after deploy./health200, semantic Manager 4xx responses preserved, repeated idempotency key returns the same run, and no Studio access with the service token.configFileunset for the Railway service, or service-token Studio access. Roll back the Agentic deployment and disable Manager Agentic integration env until corrected.