enhancement(docs and branches): correct the README, the branch difference and the Cursor rules #11

Blocker: no. This can wait. If you use Cursor or a different AI tool for the refactor, do the Cursor rules item first.

Defect

• The manual installation example uses v0.1.0.
• The README does not tell how to send flags to the container (after bug: The wp, exec and logs commands do not accept flags for the container #4).
• The README says that Docker is a prerequisite. When Docker becomes an optional capability, this text will be incorrect.
• The branch policy is: main is the release branch, and develop is the development branch. The repository does not document this policy.
• main has one commit that is not on develop (the Cursor rules). Thus, develop does not contain all of the release branch.
• .cursor/rules/project-rules.mdc on main contains incorrect statements:
  • "Domain validation prevents path traversal." The code has no domain validation (refer to bug: The site search does not stop outside $HOME, and --domain can point outside the home directory #3).
  • "Runs on Linux, macOS, and Windows." The releases are for Linux only.
  • "No direct file system modifications outside Docker." The updater replaces a file in /usr/local/bin.
• The rules also tell AI tools to "follow existing error handling patterns". These patterns have defects (refer to bug: Commands exit with code 0 when they fail, and show incorrect error text #2).

Cost

• New users get old or incorrect instructions.
• Contributors who do not know the branch policy can push to the wrong branch.
• The development branch does not include the commit that is only on main.
• AI tools that read the Cursor rules copy the defective error pattern. They also trust a validation that does not exist.

Benefit of the fix

• The documentation agrees with the code.
• The documented branch policy tells contributors where to push.
• AI tools get correct project rules.

Fix

1. Document the branch policy in the README: main is the release branch, and develop is the development branch.
2. Merge main into develop.
3. On develop, correct or remove .cursor/rules/project-rules.mdc. The next release merge takes the change to main.
4. Remove the fixed version from the manual installation example.
5. Document how to send flags to the container.