chore: initialize project docs

.project-docs/30-worklog/tasks/20260812-docker-build-command-a7c3f9.md

@@ -0,0 +1,49 @@
+# Task: Verify Docker image build command
+
+## Identity
+
+- Task ID: 20260812-docker-build-command-a7c3f9
+- Mode: Feature
+- Branch: main
+- Worktree: D:\Datas\OthersProjects\NianAIGC
+- Base commit: 196fdde83f9064cf14030e3807f326e8ed4b4342
+- Owner: codex
+- Status: Blocked
+
+## Scope
+
+- Restore the missing `.project-docs` structure with the bundled non-overwriting initializer after explicit user authorization.
+- Verify the Docker image build command from the repository's actual `Dockerfile` and `docker-compose.yml`.
+
+## Intent And Constraints
+
+- Preserve any existing project documentation; do not use initializer overwrite mode.
+- Do not change application source or Docker configuration.
+- Distinguish command/configuration verification from an actual image build.
+
+## Outcome
+
+- Added the 34 missing `.project-docs` template files without overwriting existing files.
+- Confirmed that the repository root is the Docker build context, the default root `Dockerfile` is used, no build arguments are required, and the Compose image tag is `zhinian-aigc:latest`.
+- Confirmed the direct build command is `docker build -t zhinian-aigc:latest .`; the Compose-only equivalent is `docker compose build zhinian-aigc`.
+
+## Verification
+
+- `check_project_docs.py`: passed after initialization.
+- Inspected `Dockerfile`, `.dockerignore`, `docker-compose.yml`, `package.json`, `next.config.ts`, and the deployment guidance in the README files.
+- Docker CLI 28.4.0 is installed locally, but the Docker Desktop Linux engine is not running, so an actual image build was not executed.
+
+## Follow-ups
+
+- Start Docker Desktop (or another Docker daemon) before running the build command on this machine.
+- The newly initialized canonical project-memory files still contain placeholders and should be populated through a later integration task using verified repository facts.
+- Task Documentation Gate is blocked because the required initializer-created canonical/template files are reported as protected `FOREIGN_DOC` changes in feature mode. The bundled scripts expose no no-commit/no-delete transition. Recovery requires separate explicit authorization for operations such as `release --force` and staging/committing the initialized document baseline.
+
+## Promotion Candidates
+
+- Target: canonical `.project-docs` project positioning, architecture, and current-state files.
+  Proposal: replace initialization placeholders with verified facts from the repository in a serialized integration task.
+  Evidence: the required documents now exist but retain bundled template placeholders.
+  Future impact: future planning can rely on meaningful project memory instead of treating canonical context as unknown.
+  Semantic conflicts: none identified; README text appears encoding-corrupted in the current shell and should not be copied blindly.
+  Human confirmation required: yes, before accepting positioning or architecture statements.