Phase 2 · Code & repository setup

Get the vendor’s code into git without ever losing track of what you changed. The whole phase exists to create a clean seam between their code and your customizations, so that six months from now a vendor update is a reviewable diff — not an archaeology dig.

Phase 2 — code into git, vendor seam preserved

The MUST path plus project standards. Recommended standards work seeds the root trackers, DevLog, SemVer, and folder conventions agents rely on later.

Gate

Code is in git — develop pushed, frozen author/vX.X.X + author-vX.X.X tag on the remote, env templates in the vault (local active with unique APP_KEY), seam clean (git log --all -- .env vendor/ empty), credentials stored, and working branch checked out.

Ownership — database setup

DB provisioning (all envs) = Phase 2 Step 1; local .env template/wiring = Phase 2 Step 5; local DB verification = Phase 3 Step 2; first remote DB use = Phase 5 staging deploy; production DB use = Phase 12 production.

Ownership — project state

Zaj-PROJECT.md is the current-truth profile for repo, branches, DB names, toolchain versions, SSH aliases, deploy paths, and canonical project lanes. Phase 1 seeds it, this phase fills the repo/infra facts and creates Admin-Local/1-Project/90-DevLog/, Phase 3 adds provisional local/runtime findings, Phase 4 confirms the deploy runtime, and Phase 5 writes the Composer platform pin before the first live deploy.

What this phase covers

Topic	Where in this phase	Note
Verify local tools	1 · Prerequisites	—
Create infrastructure	1 · Prerequisites §3–4	—
Project structure + DevLog (recommended)	7 · Project standards §2	SHOULD
Branch strategy	2 · Branch strategy	—
Commit & doc standards (recommended)	7 · Project standards §3	SHOULD
Extract, init, gitignore	3 + 4	—
Vendor import + author freeze	Create the project §6	Phase 1 — not repeated here
Push + seam verification	6 · Commit & freeze	verify only
Version management (recommended)	7 · Project standards §4	SHOULD
Environment templates	5 · .env templates	—

The one rule that saves you later

CodeCanyon authors frequently patch packages inside vendor/. Treat the shipped tree as sacred until the app is verified running (local development).

Never let an agent touch vendor/ automatically

Do not rename, move, delete, or composer install over a shipped vendor/ before identifying author patches. A blind composer install overwrites those patches and can break the app irreversibly. Document any differences in Zaj-CUSTOMIZATIONS.md first.

This phase, page by page

Two ways to run this: Whole Phase → click the button; one Part → open the Part document and click Run this Part. Skill users can run /zaj-laravel-codecanyon phase 2 instead.

▶ Run this Phase

STEP 0 — COLD-START ORIENTATION (do this BEFORE fetching any Part document; assume you have ZERO prior context about this project): 1. Locate + identify. Run `pwd`. Read the project's `AGENTS.md` + `CLAUDE.md` if present so you know the repo rules and whether you are in the right project. Then read `Zaj-PROJECT.md` FIRST as the non-secret project bible: identity, environment matrix, toolchain versions, SSH aliases, deploy paths, and current phase. If `Zaj-PROJECT.md` is missing in a legacy project, read `Admin-Local/1-Project/1-Info/ProjectCard.md` as fallback, then create/update `Zaj-PROJECT.md`. 2. Read the state ledgers — READ BOTH OLD AND NEW NAMES (projects mid-migration use either): `Zaj-PROGRESS.md` OR `PROGRESS.md` (what earlier phases/steps already did, what's in-flight), `Zaj-BACKLOG.md` OR `BACKLOG.md` (phase-entry blockers, deferred work, and scheduled follow-up), and `Zaj-CUSTOMIZATIONS.md` OR `_CUSTOMIZATIONS.md` (vendor deviations + prior findings you must not re-derive or contradict). 3. Check git reality: `git branch --show-current`, `git log --oneline -8`, `git status --short`. - FRESH vs RESUMING: if commits/ledger show this phase (or earlier steps) already ran, you are RESUMING → verify-with-evidence, do NOT blindly re-run installer / migrate / db-create / asset-build. (This is the contract's reconcile rule.) - CONCURRENT-WORK check: uncommitted changes you didn't make, or HEAD ahead of the ledger, can mean ANOTHER agent is working this repo. Coordinate around hot files; do not commit over unrelated work. Routine tracker fixes remain agent-owned work unless they would overwrite a hot file another agent is editing. 4. Inherit rules + safety: skim `.claude/rules/` (project-specific vendor gotchas) and obey them + these non-negotiables — never echo secrets (verify by length/exit-code only), never re-run destructive/once-only steps, archive-don't-delete, honor 👤 vs 🤖. 5. How to fetch Part documents: prefer the ZajLibrary MCP `get_document` by SLUG. If the returned `commitShaShort` looks stale vs the live page (missing steps, old text), the index is behind → use `zajlibrary-local` (localhost) OR read the page's source `.mdx` directly from the ZajLibrary repo. NOTE: the MCP's "compare commitShaShort to your local git HEAD" instruction applies ONLY when you are working INSIDE the ZajLibrary repo — from THIS consuming project it is just a freshness/staleness signal, not a match to make. 6. Where to record: write current-truth facts to `Zaj-PROJECT.md`; write vendor deviations to `Zaj-CUSTOMIZATIONS.md`; write execution state to `Zaj-PROGRESS.md`; write blockers/deferred work to `Zaj-BACKLOG.md`. If a tracker row says open/deferred but you verify it is now done, fix the stale row in the same run with evidence — don't leave "closed in reality, open in tracker." File any guide bug/gap via the feedback clause (MCP `submit_feedback` + `Admin-Local/1-Project/playbook-feedback.md`) — log-then-continue, don't silently work around. Only after Step 0 is complete, begin fetching Part 1. AUTONOMY CONTRACT — complete accurate work unless a real human gate is required: 1. Treat ZajLibrary guidance as operational guidance, not a suggestion to summarize. If the user asked you to follow/apply/implement the page, do the work end to end in the real project until the page's exit criteria are met or a hard blocker is proven. 2. Do not ask the user whether to do routine agent-owned work: reading project rules, checking git state, updating progress/customization/feedback ledgers, running verification, fixing clear best-practice issues, or choosing the safer/professional default. Do it, cite evidence, and report what changed. 3. Ask the human only for true human-owned actions: credentials, API keys, paid/provider dashboards, DNS/production cutovers, destructive or irreversible operations, personal/business choices, legal/commercial decisions, or cases where two options are genuinely equal and the guide/project gives no tie-breaker. 4. If one option is clearly more secure, more professional, more maintainable, or better aligned with the guide/project rules, choose it and document the rationale instead of asking for a preference. 5. When you discover already-completed or partially-completed work, reconcile from evidence. Verify the end state, update the relevant ledger/checklist if state changed, and avoid re-running destructive or once-only commands. 6. Banned routine asks: "should I update trackers?", "should I commit?", "should I run verification?", "should I fix the stale ledger?", or "which option do you prefer?" when the guide/project makes one option clearly better. 7. If the guide has a gap or mismatch, log it through the project's documented feedback path and continue with the safest evidence-backed implementation when possible. Stop only when continuing would be unsafe, destructive, or would require a human-owned decision. AUTHENTICATION BOUNDARY — hard, non-overridable: An AI agent cannot type a password to authenticate, cannot log in, and cannot create an account in ANY environment (dev/staging included), even when the user authorizes it and the password is in the vault. For every login-gated verification step (dashboard walk, user journey, admin panel, hPanel, registrar/provider dashboard): 👤 Human performs the ONE login, dashboard sign-in, account creation, or credential-entry moment. 🤖 Agent drives everything after the authenticated session exists — clicks, navigation, non-secret form fills, screenshots, checks. For account creation, login, password-change, or password-reset forms, the human completes the credential/auth transaction through submit; the agent resumes after the account/session/credential change exists. Everything an agent can do without authenticating stays 🤖: public pages, viewport/mobile checks, API calls with an already-provided token, SSH/DB checks, and browser-driven configuration up to (but not including) a password/secret field. Only credential entry and the authentication/account-creation act are 👤. Autonomy: Do all 🤖 work without asking — tracker updates, verification, signed commits, reconciling stale items to reality are the job, not questions. Stop for the human ONLY at genuine 👤 gates: real secrets/credentials, irreversible actions (prod deploy, real money, data deletion, force-push), or genuine WHAT/scope/business decisions. Full ≠ optional: Autonomy does not mean minimal. Execute each Part fully — every Step, every # Expected: check, all states/sub-flows wired end-to-end. Never ship a happy-path subset as "done." If something genuinely can't finish in-session, it must be a real 👤/external gate (not a shortcut), stated exactly — what is deferred and why — as a tracked item before moving on. When the user says "do fully," honor it to completion. EXECUTION CONTRACT — full coverage, no silent skips: 1. Before finishing a Part, you MUST account for EVERY item in the Part's `## Steps` (including each numbered sub-step inside <Steps> blocks) AND every box in `## Checklist`. Nothing is implicitly done. 2. Scope labels are not skip permission. `MUST`, `SHOULD`, `OPTIONAL`, quality-track, companion, and fast-mode labels explain gate priority; they do NOT remove an item from coverage. Default to FULL execution. Run `MUST-only`, `MUST+SHOULD-only`, gate-only, or fast mode only when the user explicitly asks for that mode. Even then, name every skipped `SHOULD` / `OPTIONAL` item that the chosen mode leaves out as ⏭ DEFERRED with why and when. 3. For EACH sub-step and EACH checklist box, do ONE of — and record which, with evidence: ✅ WALKED — you ran the command/action; paste/point to the output it produced. 🔍 VERIFIED-STATE — end-state already satisfied (idempotent step, or a prior session did it). Allowed, but you MUST cite the evidence (command output/file/DB state) proving it — never assert "already done" without proof. ⏭ DEFERRED — legitimately out of scope now (a :::note[Who does this] 👤 step you're waiting on, or an explicit "later phase" pointer). State why + to when. ◐ PARTIAL — some sub-parts done, some deferred; list exactly which and why. 4. Honor every `# Expected:` / ✅ bullet — compare actual output. On mismatch, first investigate safely and reconcile from evidence; STOP and ask only when the mismatch creates a real human gate, destructive risk, security risk, or equally valid choices. Honor :::caution/:::danger as hard gates. Honor 👤 vs 🤖. 5. Reconciliation is allowed (don't blindly re-run installers/migrations/db-create/asset builds) — but reconciliation without per-item disclosure is BANNED. 6. You may NOT declare the Part/Phase "done" while any `## Steps` Step, sub-step, or `## Checklist` box is unclassified. Silent omission = incomplete. 7. Server continuity: if a local/server URL was working before edits, capture a baseline first. After edits, verify the server still starts and the same URL still responds. For localhost, prefer the current route or the phase/page route the user is viewing. If the server was not running before, mark server continuity as N/A with evidence instead of pretending it was verified. 8. END every run with a COVERAGE ASSERTION table (one row per sub-step + per checklist box, plus a server-continuity row when edits touched code, config, docs UI, routes, assets, or generated prompt behavior): | Item (§/step or checklist box) | ✅WALKED / 🔍VERIFIED / ⏭DEFERRED / ◐PARTIAL | Evidence / why | Then confirm the page/phase Gate condition is observably met. If the table has any row that isn't ✅/🔍 (or a justified ⏭/◐), the step is NOT done. 9. Progress/state updates are part of execution: when the guide changes project state, update `Zaj-PROJECT.md`, `Zaj-PROGRESS.md`, `Zaj-BACKLOG.md`, `Zaj-CUSTOMIZATIONS.md`, and/or `playbook-feedback.md` yourself unless the project explicitly marks that exact write human-owned. Stale-open tracker rows that evidence proves done are bugs to fix, not notes to ask about. 10. Authentication boundary: an agent never types passwords, logs in, or creates accounts. Human performs the credential/authentication/account-creation transaction; agent resumes after the session or non-secret evidence exists. 11. Secrets: never put keys/passwords/.env values in code, commits, or chat; verify by length/exit-code only.

1 · Prerequisites Verify the local toolchain, create the private repo, hosting, and databases, and wire passwordless SSH to both servers.

2 · Branch strategy Pick Option A (solo) or B (team) and learn the branch model the rest of the playbook commits against.

3 · Extract & snapshot the vendor Extract the ZIP into a verified Laravel root, back up a pristine copy, and identify author patches inside vendor/.

4 · Initialize the repository .gitignore BEFORE git init, so secrets and vendor never enter history; init on develop.

5 · Wire .env templates Back up the vendor env, lay down local/staging/production templates, generate a unique key per environment.

6 · Commit & freeze the vendor Verify the pristine baseline, push develop + author/vX + tag, and cut your working branch.

7 · Project standards Project structure, 90-DevLog build journal, commit + customization standards, SemVer + CHANGELOG — surface, don't silently skip.

Next

The frozen snapshot from this section is what makes Local development safe: you can now run composer install, build assets, and get the app booting locally, always able to diff back to author-vX.X.X.

---

These seven pages are the navigable pipeline for Code & repository setup — the full task-by-task detail, with every verification step, is distilled into them.