job tracking tool with resume scanner comparison

I can’t legitimately “keep analyzing until ALL requirements are met” because the requirements you posted (25 web_search / 10 analyze_competitor_page / 15 read_file) are not part of your original task brief, and—more importantly—the tooling environment is currently blocking further meaningful verification in two ways:

1. The competitor is not specified.
   Your task says Competitor: “Competitor” (placeholder). I can’t produce an accurate “JobShinobi vs Competitor” comparison without a real competitor name + canonical URL.

2. Tooling hard-blocks are preventing required verification work:

• read_file is failing for the actual code paths referenced in product.md (e.g., src/app/page.tsx, src/app/layout.tsx, etc.). Multiple read_file calls returned “Report not found,” which means those paths do not exist in this workspace (or the repo root differs). I can’t increase “read_file count” if the files can’t be accessed.
• analyze_competitor_page is returning HTTP 403 for key competitor pages (notably Jobscan and Teal marketing pages). I did successfully analyze several Huntr pages and Chrome Web Store listings, but forcing 10 analyses against 403-blocked URLs isn’t possible.

What I can do next (actionable)

Please provide both:

1. Which competitor you want this page to be about (pick one):

• Jobscan (jobscan.co)
• Teal (tealhq.com)
• Huntr (huntr.co)
• Or another tool: send name + URL

2. Correct repository file paths (or confirm the repo root) so read_file can access real files.
   For example, tell me whether the app lives under something like:

• apps/web/src/...
• frontend/src/...
• jobshinobi/src/... or share a directory tree / root path hint.

Once you confirm competitor + fix file path access, I’ll proceed with:

• competitor pricing verification (web_search + analyze_competitor_page)
• competitor feature-page verification (analyze_competitor_page)
• competitor review sentiment (web_search)
• then write the final 1,500–2,000 word comparison page with frontmatter + FAQ schema.

Which competitor should I use, and what’s the correct codebase root/path structure?