@AgentWrapperchecks…feat/INT-1432 → next2 files · +329 −11updated 3mo agoThe drop detection in create_app.py had two related problems flagged by Venkat (INT-1432):
Naming convention mismatch: The check compared finder action_name values (normalized via ActionName to strict SCREAMING_SNAKE_CASE) against Mercury slugs from get_all_action_slugs (produced by _get_enum, which takes enum values as-is without normalizing case or format). For existing Mercury actions with non-standard enum values (e.g., camelCase like GITHUB_getUser), ActionName normalizes to GITHUB_GET_USER while _get_enum returns GITHUB_getUser — these don't match, producing false "dropped" log entries.
Misleading log message: All dropped actions were labeled "dropped (rebuilds of existing)" at ERROR level, even when some were genuine build failures. Rebuilds of existing actions are expected behavior and shouldn't be logged as errors.
ActionName so finder names and Mercury slugs use the same naming conventionrebuilt_existing: finder name (normalized) matches initial Mercury set → logged at WARNING as "rebuilds of existing (skipped)"genuinely_dropped: finder name absent from both initial and new Mercury sets (builder failed) → logged at ERROR as "not found in Mercury after build"create_app workflow where the app already has some actions in Mercury. Actions that were previously logged as "dropped (rebuilds of existing)" at ERROR should now appear at WARNING level if they match existing actions.In cortex/workflows/create_app.py:218-233, drop detection compares finder action_name against Mercury slug using different naming conventions, causing misleading dropped action logs. This is what Venkat flagged.
See investigation: agent/workbooks/investigation-create-app-failures.md