|
|
|
|
# Virt Cloud development rules
|
|
|
|
|
|
|
|
|
|
- This repository is the independent Virt Cloud project. Work only inside this
|
|
|
|
|
checkout unless the user explicitly authorizes changes to another project.
|
|
|
|
|
- When a task depends on historical decisions, test results, or project
|
|
|
|
|
context, and the knowledge vault is available, first read
|
|
|
|
|
`/Users/admin/Documents/www/codex-knowledge/AGENTS.md`, then
|
|
|
|
|
`Memory/INDEX.md` and `Memory/CURRENT.md`; follow only the linked notes
|
|
|
|
|
relevant to the task. If the vault is unavailable, say so explicitly and do
|
|
|
|
|
not guess the old project state.
|
|
|
|
|
- The Git remote is `https://g.luoli.live/root/virt.git`.
|
|
|
|
|
- All subsequent changes, commits and pushes for this project must use the
|
|
|
|
|
`venix` branch. Do not commit or push them to `main` or force-push.
|
|
|
|
|
- Before editing or committing, check the current branch and working tree.
|
|
|
|
|
Preserve unrelated user changes. If this checkout is not on `venix`, stop
|
|
|
|
|
before changing files and resolve the branch safely.
|
|
|
|
|
- Never commit real configuration, credentials, private keys, database dumps,
|
|
|
|
|
installed dependencies, runtime logs or caches. Keep source configuration
|
|
|
|
|
examples and source schema files versioned.
|
|
|
|
|
- The PHP application lives in `web/`; its eventual HTTP document root is
|
|
|
|
|
`web/public/`, not the repository root.
|
|
|
|
|
- Only the venix theme is retained. Ordinary users must not receive host
|
|
|
|
|
administration or retired node-management routes.
|
|
|
|
|
- PHP owns accounts, wallet purchases, orders, public-key ownership and public
|
|
|
|
|
HTTP authorization. The Python engine owns libvirt, host credentials and VM
|
|
|
|
|
operations. Keep the engine private and authenticate every internal request.
|
|
|
|
|
- Purchases provision one VM from the plan snapshot. Each purchase or renewal
|
|
|
|
|
creates an independent prepaid service period with its own traffic quota.
|
|
|
|
|
An exhausted quota disconnects VM networking until the next paid period;
|
|
|
|
|
final expiry disconnects networking without powering off the VM. An unpaid
|
|
|
|
|
renewal invoice enters a three-day grace period and then permanently removes
|
|
|
|
|
the VM definition and its panel-managed disks. Never replay an ambiguous
|
|
|
|
|
destructive operation or refund it without confirmed cleanup; reconcile its
|
|
|
|
|
operation identifier.
|
|
|
|
|
- Users share the original VM-panel styling; administrator pages retain venix.
|
|
|
|
|
- See `docs/PRUNING_REPORT.md` for retained/removed feature boundaries and
|
|
|
|
|
`docs/INTEGRATION_PLAN.md` for the planned Python engine integration.
|