New development session: read the short AGENTS.md entry and the assigned issue's latest owner comments and claims on the Inkseq Delivery board. Expand linked contracts only as needed; workflow/project.json contains board identifiers. Preserve older checkouts. Use English on GitHub; merged source, a published release and verified live usability are separate states.
Inkseq provides one business API for Quick Chat, Yingxu story creation and external agents at https://inkseq.com. The www hostname and the previous product domains redirect to that origin after the verified cutover. Host-bound login cookies require one new login; existing API keys and Agent grants keep their original authority and expiry. Follow the public Agent guide or download the skill.
The generation runtime uses WanGP; historical Comfy routes remain for original-job recovery and rollback. Backend source is platform_app.py / studio_platform/; deployment definitions are in deploy/platform/. Internal sixnine identifiers, tenant IDs and encrypted credential records remain compatible. These source boundaries do not establish live GPU availability.
| Need | Entry and authority |
|---|---|
| Product direction and work packages | PROJECT-PLAN.md |
| Durable choices, rationale and revisit conditions | DECISIONS.md; acceptance of a decision is not release evidence |
| Required generation behavior | GENERATION-CONTRACT.md and the specific contract/specification linked by the issue |
| Latest recorded implementation/deployment observations | CURRENT-BASELINE.md; dated evidence, not live health |
| Ownership, current task status and acceptance | Delivery board, linked issues/PRs and WORKFLOW.md |
| Historical design, implementation reports and local research | PLANNING-INDEX.zh-CN.md; follow its scope and date labels |
Material durable decision changes update the record and affected plan/contract together. Historical reports explain a past revision; they do not override current contracts or authorize operating a service.
- Development checks and scoped releases, platform deployment, release and rollback.
- API usage, backup/recovery and operations: use the applicable implementation/version and current authorization; these procedures are not health reports.
- Earlier architecture, five-minute walkthrough, delivery report, readiness review and iteration evidence: dated background, not the active task list or proof of today's deployment.
- Infrastructure/cost observations and DNS cutover: verify the recorded scope, destination and date before use; old prices, endpoints and rollout windows are not current authority.
Canonical frontend and approved mock live in the public inkseq/inkseq-design repository at ../video-studio-design/studio-app and ../video-studio-design/quick-chat-mock. The backend is inkseq/h3-studio. The active Delivery Project is the private inkseq organization project; its verified item, field and view identifiers are recorded in workflow/project.json. Historical evidence retains its original links. This repository's yingxu/ is a generated release snapshot maintained by tools/sync_yingxu_source.py. Edit canonical source; do not directly edit the snapshot, publish unapproved UX, or put local drafts/media into images.
The earlier standalone MiniMax H3 website, separate password database and deployment path were retired after the #257 deployed-runtime inventory. Their source remains recoverable in Git history; current platform authentication, jobs and recovery use studio_platform/. The expert visual workflow is retained as a test fixture. This retirement does not remove any host database, media, original-job recovery code or rollback image.
Its older documentation described a CPU-only website deployment with generation disabled and a fixed test account set. That description is historical, not the current public generation or authentication state. Consult the dated baseline and exact release evidence before operating any deployment.
- Lightsail and GitHub Actions deployment
- Multi-GPU / API routing design and remaining work
- Generation controls and measured limits
Use the scoped development/release workflow to select checks for the final change. Test layout and focused commands explain discovery and shared fixtures. The broad compatibility command below is a reference, not a requirement to run the full suite for every small edit.
Python 3.12, Node.js and FFmpeg/ffprobe are required:
python -m pip install -r requirements.lock.txt
python -m unittest discover -s tests -p 'test_*.py' -vTests use disposable data and fake requests. Do not run live generation scripts as a CI test. Database, media, cloud state, SSH files, model weights, credentials, logs and local experiments are deliberately excluded from Git and Docker.
GitHub Actions runs CI on push/PR. CPU deployment is an explicit main-branch workflow dispatch after destination configuration and account provisioning. The tested image is passed to deployment unchanged. This repository alone does not create an AWS account, Lightsail instance, domain, GPU, or API subscription.