Meta Community by Legion Code Inc.
Review Meta inboxes, prepare replies, preview moderation and export leads through scoped Zernio workflows. Install Meta Foundation and its selected Wasp Nest Core prerequisite before native invocation.
| Command | Output |
|---|---|
review-my-inbox | Private prioritized queue with source/coverage evidence; no seen receipt |
draft-my-replies | Exact private reply drafts and unapproved action proposals |
moderate-my-comments | Reviewed comment policy decisions and visibility previews |
export-my-leads | Private JSON/CSV files, source hashes and a redacted completeness manifest |
Guides
- Community skill and guide map
- Leads skill and guide map
- Foundation contracts (
../meta-foundation/contracts/README.md; source reference, not bundled; resolve the selected prerequisite owner)
Offline tools
Run from this source checkout with the approved Python environment:
.venv-meta-suite/bin/python -m packs.meta-community.skills.meta-community-stinger.scripts.community_tools --help
.venv-meta-suite/bin/python -m packs.meta-community.skills.meta-leads-stinger.scripts.lead_tools --help
.venv-meta-suite/bin/python -m pytest tests/plugins/community tests/plugins/leads -q
Installed hosts resolve the actual Foundation pack and artifact runtime; pass its path through --foundation-root where the source sibling layout is unavailable. Source files and a packaged menu entry do not prove native installed invocation.
The helper request selects one resolved Foundation scope per run. Evidence references point to hash-verified private files whose pages contain collected observations. Raw source pages use opaque cursor and next_cursor fields and a conversations or leads array. Host collection adapters map native envelopes into this local capture without inventing completeness. Multi-account work runs separately per account and combines only labeled summaries.
Community review output contains identifiers, triage states and hashes; raw message text remains private evidence. Action previews reuse a supplied canonical Foundation change proposal, validate the exact target/request/hash and force an unapproved draft. The helper never creates approval receipts or executes requests.
Lead export requires a private workspace outside source/plugin trees and creates a new bundle without overwriting an existing export. CSV is escaped for spreadsheet-significant prefixes; private JSON retains original values and null/empty/missing distinctions. Never publish row-level exports with a plugin or client report.
Boundaries
Message reads do not mark read. Explicit seen receipts, replies, moderation, form/status/test-lead changes and workflow activation are separate effects. Source build approval does not authorize any of them. Current active-workflow graph documentation conflicts are retained in research; no live workflow is used to resolve them automatically.
Raw research, tests and private runtime data are excluded from generated distributions. Component research is source evidence, not account-specific acceptance. Security then Quality and orchestrator Repository Health remain required before any approved commit/push.