Skip to content

Overlap With Canonical Repos

Backend (someli-mono-repo/backend/ vs someli-api/)

49 file-level differences as of audit time, ignoring node_modules, .git, .nuxt, .yarn, lockfiles, working-tree-only files (doc/, CLAUDE.md, .env, scratch images), and routes/temp_video_* directories.

Concrete differences observed:

  • Only in canonical someli-api (added after the snapshot): csv_image_ideas_search_terms.js, csv_image_ideas_search_terms.py, deploy_image.py, gemini_content.py, job_carousel_pdf.js
  • Modified files (sampling): dashboard/routes/index.js, .github/workflows/dev-api-deploy.yml, .gitignore, helper/functionsForAi/getAiParameters.js, helper/getRagData.js, helper/helper.js, helper/index.js, job_auto_post.js, job_content_schedule.js, job_csvFileUpload.js, job_dynamic_post_generation.js, job_excel_to_library.js, job_facebook_carousal_publish.js, job_holiday_post_branding.js, job_instagram_carousal_publish.js, …

Most of the diffs are in helper/, the larger job_*.js files, and the dashboard module — the parts of someli-api that change most often.

The snapshot is roughly 2-3 months behind the canonical (snapshot last touched 2026-01-20; canonical at audit time was 2026-04-16).

Frontend (someli-mono-repo/frontend/ vs someli-platform/)

333 file-level differences as of audit time, using the same exclusions.

The diffs span most of components/, much of pages/, parts of store/, the nuxt.config.js, package.json, and the Polotno bundle. The frontend canonical has moved significantly since the snapshot was taken (the entire customer-facing UI has accumulated months of feature work).

Notable structural divergence:

  • The canonical someli-platform/assets/css/plyr-theme.css exists; the snapshot does not have it.
  • All four api/*.js server-middleware files differ.
  • Most components/*.vue files have been modified in the canonical.

Net assessment

The someli-mono-repo snapshot is substantially stale on the frontend and moderately stale on the backend. It is suitable for archival reference, not for running. Do not deploy from it. Do not use it as the basis for new feature work.

If you find yourself relying on this snapshot, raise it with the team — either ask for a refresh, or argue for retiring the snapshot in favour of someli-project (which carries the additional admin/designer pairs and is closer to up-to-date for those).