Fix ROI reporting docs: table names, file structure, and commands

[ko47kmr]

Summary

• Fix table name inconsistencies across documentation: revenue → revenue_table, event_master → events_master (matching actual table names created by the workflow)
• Update project structure in top-level README to match actual file layout (old references to system_prompt.md, tools.yml, forms/ replaced with current Dashboard Viz/, knowledge_bases/, form_interfaces/)
• Fix tdx agent push flag: -y → -f (correct flag per CLI help)
• Update workflow README: td workflow push → tdx wf push, add tdx.json creation step, add concrete tdx wf secrets set command
• Clarify revenue_table setup: sample data generation is for testing only; production use requires user-provided actual conversion/revenue data
• Allow independent setup of agent and workflow components (agent can be deployed without running the workflow if tables already exist)
• Remove internal references not appropriate for external users
• Fix event_master → events_master in Japanese Knowledge Base specs

Files Changed

File	Changes
roi_reporting/README.md	Table names, file structure, setup steps, troubleshooting
agent/README.md	-y → -f (2 places)
agent/README_JA.md	-y → -f (2 places)
agent/knowledge_bases/OverallSummary_Spec_ja.md	event_master → events_master (3 places)
agent/knowledge_bases/CampaignDetails_Spec_ja.md	event_master → events_master (1 place)
workflows/reporting_agent/README.md	CLI commands, tdx.json step, revenue table docs, remove internal ref

Test plan

• Verify tdx agent push . -f works with updated README instructions
• Verify all table names in docs match config.yaml definitions (events_master, revenue_table, daily_summary, email_events)
• Verify project structure in README matches actual file listing

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the ROI reporting documentation to match the current workflow/agent setup, table names, CLI commands, and repository file layout, removing internal-only references and clarifying how revenue data should be handled.

Changes:

• Standardize documented table names to match the workflow outputs (e.g., revenue_table, events_master).
• Update setup instructions/CLI commands (e.g., tdx agent push ... -f, tdx wf push, workflow secret-setting guidance).
• Refresh README project structure and clarify that workflow and agent setup can be done independently.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
engage-box/roi_reporting/workflows/reporting_agent/README.md	Updates workflow setup steps/commands, adds tdx.json creation guidance, clarifies sample revenue behavior, removes internal note.
engage-box/roi_reporting/README.md	Aligns table names and project structure docs; clarifies independent setup paths.
engage-box/roi_reporting/agent/README.md	Fixes tdx agent push flag usage (-y → -f).
engage-box/roi_reporting/agent/README_JA.md	Same tdx agent push flag fix for Japanese README.
engage-box/roi_reporting/agent/knowledge_bases/OverallSummary_Spec_ja.md	Updates table reference event_master → events_master.
engage-box/roi_reporting/agent/knowledge_bases/CampaignDetails_Spec_ja.md	Updates table reference event_master → events_master.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The project structure tree lists workflows/reporting_agent/tdx.json, but that file is not present in the repository. Either add/commit the workflow tdx.json, or update this tree to indicate it’s user-created (as described in workflows/reporting_agent/README.md) rather than part of the checked-in layout.

Suggested change

	├── tdx.json # Workflow project reference
	├── tdx.json # User-created local workflow project file (not committed)

[Copilot]

This section says the tables are “to be created by the workflow”, but the revenue_table row indicates it may be user-provided. Consider rewording to “tables required to exist” (and then specify which ones the workflow creates vs. must be provided) to avoid a contradiction.