14 lines
1.5 KiB
Markdown
14 lines
1.5 KiB
Markdown
# Ghostwire project instructions
|
|
|
|
The project name is Ghostwire. Keep the existing `whatsapp.py` launcher, `whatsapp_suite` package and configured repository URL unless explicitly migrating them.
|
|
|
|
For clickable local Windows file links, use the actual absolute path starting with `C:/`, never `/C:/`. Wrap Markdown targets containing spaces in angle brackets. This format was confirmed to work in Karl's chat on 2026-10-11.
|
|
|
|
Use `whatsapp_suite/` as canonical source. `whatsapp.py` is generated; rebuild it after changing Python, assets or tests. Documentation-only changes do not require rebuilding.
|
|
|
|
Start with [CONTRIBUTING.md](CONTRIBUTING.md) for the change workflow. Repository-specific agent guidance is in [skills/whatsapp-suite-development/SKILL.md](skills/whatsapp-suite-development/SKILL.md). Read [architecture](docs/ARCHITECTURE.md) and [validation](docs/VALIDATION.md) before changing native integration or making compatibility claims.
|
|
|
|
Run source and portable offline tests for implementation changes; inspect skips. Keep default tests free of live side effects. Preserve native object/ABI checks, advisory compatibility reporting, explicit self-message recipient guards, uncertain-send receipt handling and HTTP acknowledgement semantics.
|
|
|
|
Do not commit exports, real message/contact fixtures, profiles, credentials or research captures. Do not install tasks or send messages solely to verify documentation. User authorization determines live actions and publication scope.
|