@codyswann/lisa 2.195.4 → 2.195.6

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-roles/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: lisa-wiki-connector-roles
+description: "Ingest the wiki's own…"
+---
+
+# lisa-wiki-connector-roles
+
+A universal, deterministic connector backed by `scripts/ingest-roles.mjs`. It captures the roster so
+the wiki documents its own digital staff.
+
+## Flow
+```
+node "${PLUGIN_ROOT}/scripts/ingest-roles.mjs" --config wiki/lisa-wiki.config.json \
+  --wiki wiki --source-dir wiki/sources/roles \
+  --state wiki/state/roles/roles.json --emit-meta wiki/state/handoff/roles-<runId>.json
+```
+Hand the source note + proposed cursor back to `lisa-wiki-ingest`.
+
+## Rules
+- Reads `config.staff[]` and `wiki/staff/*.md` only; never invokes/schedules the role subagents
+  (that is out of scope — see lisa-wiki-add-role).
+- Writes only its source note + handoff meta; the kernel advances state.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-roles/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Connector Roles"
+short_description: "Ingest the wiki's own…"
+default_prompt:
+  - "Use $lisa-wiki-connector-roles: Ingest the wiki's own…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-slack/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: lisa-wiki-connector-slack
+description: "Ingest a Slack channel into…"
+---
+
+# lisa-wiki-connector-slack
+
+The centralized Slack connector backed by `scripts/slack_oauth_user.py` (one-time OAuth) and
+`scripts/ingest_slack_channel.py` (ingest). These are the stdlib-Python scripts previously duplicated
+verbatim across projects, now shipped once by the plugin.
+
+## Side effects — `external-write`
+Slack OAuth opens a browser and writes a user-token file to a local secrets path. The slack connector
+is therefore `external-write`: it runs ONLY with config opt-in **and** explicit per-run intent, is
+skipped during an unattended full ingest, and its PR never auto-merges.
+
+## Flow
+1. One-time auth (explicit): `python3 "${PLUGIN_ROOT}/scripts/slack_oauth_user.py"` — stores a
+   `xoxp-` user token under an ignored secrets path. The token file is never committed.
+2. Ingest: `python3 "${PLUGIN_ROOT}/scripts/ingest_slack_channel.py" --channel <id-or-name> \
+   --config wiki/lisa-wiki.config.json --emit-meta wiki/state/handoff/slack-<runId>.json` — verifies
+   the Slack tenant against config, then writes sanitized source notes under `wiki/sources/slack/`
+   (tokens/keys redacted) and emits a **proposed** cursor to the handoff file.
+3. Hand the source notes + handoff meta back to `lisa-wiki-ingest` (the kernel advances final state
+   after verification).
+
+## Rules
+- Verify the Slack team/tenant matches config before ingesting.
+- Token/OAuth artifacts stay in `.gitignore` and are never committed.
+- Writes only Slack source notes; the kernel performs synthesis/index/log/verify/PR.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-slack/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Connector Slack"
+short_description: "Ingest a Slack channel into…"
+default_prompt:
+  - "Use $lisa-wiki-connector-slack: Ingest a Slack channel into…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-web/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: lisa-wiki-connector-web
+description: "Ingest a public URL into a…"
+---
+
+# lisa-wiki-connector-web
+
+Skill-driven connector. Fetches a public URL (WebFetch / equivalent), reduces it to a reader-safe
+source note, and hands off; the kernel does synthesis/index/log/verify/state/PR.
+
+## Flow
+1. Confirm `connectors.web.enabled` and `sideEffects: read-only-ingest`.
+2. Fetch the URL read-only (WebFetch). Do not follow suspicious cross-host redirects without care.
+3. Write a source note under `wiki/sources/web/<YYYY-MM-DD>-<slug>.md` with frontmatter
+   (`type: source`, dates, `source_system: web`, the URL) and a faithful, reader-safe summary +
+   key excerpts. Redact secrets; honor `sourceRetention` (e.g. `external-pointer-only` keeps just the
+   URL + minimal note).
+4. Emit run metadata (the source-note path) to the handoff file; return to `lisa-wiki-ingest`.
+
+## Rules
+- Read-only; never submit forms or trigger actions on the page.
+- Do not invent content not present on the page; weak/uncertain material → open-questions.
+- Writes only the source note + handoff meta; the kernel advances state.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-connector-web/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Connector Web"
+short_description: "Ingest a public URL into a…"
+default_prompt:
+  - "Use $lisa-wiki-connector-web: Ingest a public URL into a…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-doctor/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: lisa-wiki-doctor
+description: "Verify that a wiki is correctly…"
+---
+
+# lisa-wiki-doctor
+
+The post-migration / post-setup verification checklist. Orchestrates the deterministic scripts and
+functional smoke tests, then writes `wiki/state/migration/doctor-report.json` and prints the blocking
+items.
+
+## Verdict
+Each item is `PASS | WARN | FAIL | SKIP`; overall is `READY | READY_WITH_WARNINGS | NOT_READY`. In
+hard-enforcement mode (`--migration` after phase 5) `WARN` on structure/integrity items is not
+allowed; earlier phases allow documented legacy warnings. Build checks (group G) are Lisa/release-only
+and `SKIP` in downstream repos.
+
+## Checklist
+- **A. Structure & config** (deterministic): `validate-config.mjs` + structure-manifest conformance;
+  required files present; `schemaVersion` set and rendered `kernelVersion` matches the installed
+  plugin; README mode recorded (never implicit `stub`).
+- **B. Integrity & safety** (deterministic): `lint-wiki.mjs` + `diff-guard.mjs`; index/log coverage;
+  state-order invariant; no broken/orphan links; secret/tenant/contamination/sensitivity scans;
+  memory sources project-scoped only (no global Codex memory / Chronicle).
+- **C. No-loss / parity**: pre/post manifest maps every legacy page/doc/command/ingest-path/role;
+  nothing dropped; docs absorption idempotent with zero dangling links; old README ingested before
+  rewrite; no leftover project-local machinery except generated overlays + role agents.
+- **D. Runtime surfaces** (both runtimes): canonical commands resolve on Claude; `$lisa-wiki-*` on
+  Codex; each `config.staff[]` role has its doc page + both subagents; MCP doctor passes or connector
+  cleanly disabled; external-write connectors skipped unless explicit intent.
+- **E. Functional smoke** (skill-orchestrated): targeted ingest of a small fixture exercises the full
+  ordered pipeline (in the migration branch or dry/scratch mode — **no extra PR**); `/query` returns
+  a cited answer; `/lint` clean (or expected phase warnings); `/onboard-me` completes read-mostly with
+  no PII; bare `/ingest --dry-run` lists non-external-write sources; `/doctor` rerun is idempotent.
+- **F. Mode-specific**: embedded self-ingest at HEAD; wrapper child-docs ingested-not-moved and not
+  staged; standalone/subdir path resolution; no-PR mode does not require PR creation.
+- **G. Git / CI / distribution** (deterministic): clean working tree (only intended changes); no
+  secrets/OAuth committed; PR/auto-merge policy honored; CI validator green if `--with-ci`; (Lisa
+  only) `bun run build:plugins` builds both artifacts and `check:plugins` passes.
+
+## Notes
+- Deterministic items are run by `scripts/verify-migration.mjs` (which emits the JSON report); this
+  skill adds the functional smoke tests and interprets phase-allowed warnings.
+- Read-mostly: the smoke tests must not open an extra PR or perform external writes.
+
+## Related
+`lisa-wiki-migrate`, `lisa-wiki-lint`, `lisa-wiki-setup`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-doctor/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Doctor"
+short_description: "Verify that a wiki is correctly…"
+default_prompt:
+  - "Use $lisa-wiki-doctor: Verify that a wiki is correctly…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-ingest/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: lisa-wiki-ingest
+description: "Ingest source material into the…"
+---
+
+# lisa-wiki-ingest
+
+The single entry point for getting knowledge into the wiki. It is a **router**: it never reimplements
+synthesis per source — it selects a connector to produce a sanitized source note, then the kernel
+performs the shared, ordered pipeline.
+
+## Modes
+- **Targeted:** `/ingest <url|file|prompt>` — ingest one source. Classify the input and pick the
+  matching connector.
+- **Full:** `/ingest` (no argument, or "do a full ingest") — iterate **every enabled connector whose
+  side-effect policy permits unattended ingest**: self + other registered projects' git/PR history,
+  project-scoped memory, roles, plus read-only registered sources (notion, jira, confluence,
+  quickbooks, …). `external-write` connectors (Slack OAuth, CRM writeback) are **skipped unless the
+  run includes explicit external-write intent**.
+- **Dry run:** `/ingest --dry-run` — list the sources a full ingest would run; perform no writes.
+
+## Step 0 — resolve the wiki root (once per run)
+
+Before anything else, run `node scripts/ensure-wiki.mjs --json` and use the returned `wikiRoot` as the
+base for the whole pipeline — never hardcode `wiki/`. This is mode-agnostic by design:
+
+- **Local wiki** (no `wiki.source` in `.lisa.config.json`) — resolves the in-repo wiki root instantly;
+  the branch sync below proceeds against **this** repo's remote, exactly as before.
+- **Remote wiki** (`wiki.source.url` set) — `ensure-wiki` mirrors/refreshes the gitignored working copy
+  of the canonical wiki repo and returns its path. In this mode the "sync the branch" step below, and
+  the Commit/PR step (7), operate against the **wiki repo's own remote** (the mirror), not the host
+  project's `origin`. The host project repo is never written to.
+
+## Before ingesting — sync the branch (once per run)
+
+Run this **once per ingest invocation, before any source is processed** (skip for `--dry-run`, which
+writes nothing). The point is to ingest on top of fresh state, never stale state. Operate in the wiki
+root resolved in Step 0 — the host repo for a local wiki, the mirror for a remote one.
+
+1. **Resolve the default remote branch** — `gh repo view --json defaultBranchRef -q .defaultBranchRef.name`,
+   or `git remote show origin | sed -n 's/.*HEAD branch: //p'`, or the `origin/HEAD` symbolic ref. If
+   the repo has no remote, note "no remote — skipping branch sync" and proceed.
+2. **Fetch** — `git fetch <remote>` to update remote-tracking refs.
+3. **Bring the working branch up to date with the default remote branch** so the ingest lands on
+   current state:
+   - On the default branch → fast-forward to `<remote>/<default>` (`git pull --ff-only`).
+   - On a non-default branch → merge or rebase `<remote>/<default>` in (per the project's convention)
+     so the branch is not behind the default.
+4. If the sync cannot complete cleanly (merge conflict, diverged history, or a dirty tree that would
+   conflict), **stop and surface it** rather than ingesting on top of stale or conflicted state — the
+   human resolves and re-runs. **Never discard unrelated working-tree changes** to force a sync.
+
+## The ordered pipeline (per source) — never reorder
+1. **Connector** validates (tenant guard + auth), reads its state cursor (first-run vs incremental),
+   fetches read-only, and writes a sanitized **source note** under `wiki/sources/<system>/` plus run
+   metadata. A connector writes *only* its source note + metadata — never synthesis/index/log/state.
+2. **Synthesis** (kernel): distill durable knowledge into the appropriate category pages, with
+   citations back to the source note. Weak/uncertain material → `wiki/open-questions/`, never asserted.
+3. **Index**: update `wiki/index.md`.
+4. **Log**: append a `wiki/log.md` entry (fixed operation vocabulary).
+5. **Verify**: `git diff --check`, secret/tenant/contamination scans, touched-file guard.
+6. **State**: advance the connector's `wiki/state/<system>/*.json` cursor — only now, after 1–5 pass.
+7. **Commit/PR**: commit only the ingestion changes per `config.git` policy. If the ingest started on
+   the default branch, create a dedicated ingestion branch first — never commit ingestion straight to
+   the default. Push the branch and **open a PR targeting the default remote branch** (via the host's
+   PR mechanism — e.g. `gh pr create --base <default>`). Before enabling auto-merge, feed the safety
+   scan output into `createWikiIngestPublicationPolicy` from `scripts/wiki-safety.mjs`. Enable
+   auto-merge only when `autoMergeAllowed` is true. `external-write` runs, redacted runs, and any run
+   with sensitive findings are the exception — open the PR **without** auto-merge so a human reviews
+   them before it lands. The PR summary must include the policy's safe review summary: counts and
+   entity types only, never raw values, ranges, tokens, source snippets, or scanner output. If
+   auto-merge cannot be enabled (the host doesn't support it, branch protection forbids it, or the
+   policy requires review), leave the PR open and note that a human must merge.
+
+## Rules
+- **Bookend every ingest with git hygiene:** sync the branch with the default remote branch *before*
+  writing (see "Before ingesting"), and *after* a successful ingest open a PR to the default remote
+  branch with auto-merge enabled when possible — never auto-merging `external-write`/sensitive runs.
+  `--dry-run` does neither (it writes nothing).
+- Source-note-before-synthesis; state advanced **only** after verification.
+- Project-scoped only; memory ingestion never touches global/Codex-global stores.
+- Respect `sourceRetention` and `sensitivity`; do not invent facts.
+- Before advancing state or committing, run the generated-output safety gate
+  (`scripts/verify-wiki-safety.mjs`) against the wiki files/source notes produced by
+  the ingest. The default built-in scan blocks unredacted private keys, tokens, and
+  common financial/person identifiers without printing raw values. Projects may
+  select `--scanner gitleaks` for local parity with Gitleaks, and may use
+  `--scanner trufflehog` as a stricter optional verification pass when installed;
+  if a selected scanner is unavailable, keep the ingest blocked for review.
+- Redaction and review policy is centralized in `scripts/wiki-safety.mjs`. Treat
+  `reviewRequired` or any summarized finding as a hard auto-merge stop. Use the
+  generated PR summary text as-is or preserve its shape so reviewers see entity
+  types and counts without raw sensitive values.
+- Connector execution and the connector contract are detailed in the connector skills (M2+); this
+  router defines and enforces the ordering and side-effect rules above.
+
+## Related
+`lisa-wiki-add-ingest` (scaffold a custom front-door that chains here), `lisa-wiki-query`,
+`lisa-wiki-lint`, `lisa-wiki-doctor`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-ingest/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Ingest"
+short_description: "Ingest source material into the…"
+default_prompt:
+  - "Use $lisa-wiki-ingest: Ingest source material into the…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-lint/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: lisa-wiki-lint
+description: "Health-check the LLM Wiki"
+---
+
+# lisa-wiki-lint
+
+Run the wiki's integrity checks and report findings by severity. Lint is **read-only**: it diagnoses,
+it does not repair (use `/ingest`, `/setup`, or `/migrate` to fix).
+
+## What it checks (deterministic core via `scripts/lint-wiki.mjs`)
+- **Frontmatter** present/valid where required (per `schema/page-frontmatter.schema.json`).
+- **Index coverage**: every page appears in `wiki/index.md`; no index rows point at missing pages.
+- **Log coverage**: material changes have `wiki/log.md` entries.
+- **Links**: no broken internal links; no orphan pages (unreferenced and unlinked).
+- **State ordering**: no state cursor advanced without its source notes + synthesis + index + log.
+- **Structure**: files conform to `schema/wiki-structure.schema.json` (canonical locations).
+- **Safety**: secret patterns, tenant/contamination terms, stray binaries, child-repo contents
+  staged in wrapper mode.
+
+## What it checks (LLM-assisted)
+- **Contradictions** between claims; **stale** claims (older than the configured staleness window);
+  **coverage gaps** vs the wiki's stated `purpose`.
+
+## Output
+A report grouped by severity, with each item marked `PASS | WARN | FAIL`. During phased migration,
+legacy issues are reported as `WARN`; in hard-enforcement mode structural/integrity issues are `FAIL`.
+Read-only: lint prints the report and does not modify the wiki (it does not write a `LINT` log entry).
+
+## Related
+`lisa-wiki-doctor` (broader post-migration verification that runs lint among other checks),
+`lisa-wiki-ingest`, `lisa-wiki-setup`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-lint/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Lint"
+short_description: "Health-check the LLM Wiki"
+default_prompt:
+  - "Use $lisa-wiki-lint: Health-check the LLM Wiki."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-migrate/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: lisa-wiki-migrate
+description: "Migrate an existing…"
+---
+
+# lisa-wiki-migrate
+
+Move a repo's bespoke wiki onto the kernel without breaking it or producing one giant diff. Each
+phase is a reviewable change; nothing legacy is deleted until its replacement is parity-checked.
+
+## Migration invariant — rename, never lose
+Any unique command, ingest path, or role is migrated **as though created via** `/add-ingest`
+(front-door skill) or `/add-role` (subagent); wiki-ingest aliases (`*-wiki-ingest`, custom `/ingest`
+routers, …) are renamed to the canonical `/ingest`. **Loss of functionality or data is not
+acceptable** — for each migrated artifact, run the old path and the new path and diff the output
+before deleting the old one.
+
+## Phases (per repo; one reviewable change each)
+- **0 — Inventory.** Profile the repo: mode, root, categories, frontmatter coverage, log/index
+  format, source dirs, state files, connectors, runtime surfaces, MCP config, scripts, PR policy.
+  Write a pre/post manifest mapping every legacy page, source note, doc, command, ingest path, role.
+- **1 — Adopt kernel (no content rewrite).** Add `wiki/lisa-wiki.config.json`, render the contract
+  snapshot, add `wiki/state/README.md`, run validators in **warning** mode.
+- **1b — Documentation absorption & structure.** `scripts/absorb-docs.mjs` moves the host repo's own
+  docs (`docs/`, `specs/`, top-level docs) into `wiki/documentation/`, ingests them, and conforms to
+  the structure manifest; `scripts/rewrite-refs.mjs` rewrites every internal link/citation/index
+  entry (zero dangling links). Keep-in-place files stay at conventional paths. **Ask** the README
+  mode (default `rich`; `stub` only on explicit choice). Wrapper mode moves only host docs, never
+  child-project docs. Idempotent (source fingerprints); parity-checked.
+- **2 — Runtime consolidation.** Replace duplicated local wiki skills with the plugin's; bespoke ones
+  become `/add-ingest` front-doors or `/add-role` subagents. Claude commands become facades.
+- **3 — Connector consolidation.** Centralize shared connectors (e.g. Slack); keep org-specific ones
+  as contrib/overlay.
+- **4 — Normalize by touch.** New/touched pages get frontmatter; new logs use the canonical table;
+  legacy stays parseable until deliberately migrated.
+- **5 — Hard enforcement.** Flip validators to hard-fail (and enable CI) once the baseline is clean.
+
+## Finish
+Run `lisa-wiki-doctor --migration`. The repo is not considered migrated until the verdict is `READY`
+(or a human-approved `READY_WITH_WARNINGS`). Roll back by reverting the migration change.
+
+## Related
+`lisa-wiki-doctor`, `lisa-wiki-setup`, `lisa-wiki-add-ingest`, `lisa-wiki-add-role`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-migrate/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Migrate"
+short_description: "Migrate an existing…"
+default_prompt:
+  - "Use $lisa-wiki-migrate: Migrate an existing…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-onboard-me/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: lisa-wiki-onboard-me
+description: "Onboard a user to the project…"
+---
+
+# lisa-wiki-onboard-me
+
+Bidirectional onboarding: learn who the user is *in relation to this project*, then teach them what
+the project is and how to use the wiki. The minimal project README points here.
+
+## Workflow
+1. **Interview** (brief): the user's role, goals, and what they intend to do in this project.
+2. **Capture** to **project-scoped memory only** — Claude's per-project memory; on Codex only if a
+   project-scoped memory store exists. If none exists, keep it session-local. **Never** write the
+   capture into global memory and **never** commit PII into the wiki.
+3. **Tour:** summarize the project from `wiki/start-here.md` + the wiki's `purpose`, show the folder
+   map (categories), and point at the key entry pages.
+4. **Sample questions:** offer a handful of `/query` prompts tuned to the user's role to get them
+   productive immediately.
+
+## Modes
+- Default: **read-mostly, no PR.**
+- `--save-memory`: persist the capture to project-scoped memory.
+- `--write-audience-note`: write a sanitized, **non-PII** audience/role note into the wiki via the
+  normal PR flow — only when `onboarding.allowAudienceNote: true` in config.
+
+## Rules
+- Project-scoped only; global Codex memory and the Chronicle store are never used.
+- Do not auto-create a staff role; offer `/add-role` only if the user is taking on a durable project
+  function (not merely onboarding).
+
+## Related
+`lisa-wiki-query`, `lisa-wiki-usage`, `lisa-wiki-add-role`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-onboard-me/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Onboard Me"
+short_description: "Onboard a user to the project…"
+default_prompt:
+  - "Use $lisa-wiki-onboard-me: Onboard a user to the project…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-query/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: lisa-wiki-query
+description: "Answer a question from the LLM…"
+---
+
+# lisa-wiki-query
+
+Answer from the wiki, with citations, without changing it (by default).
+
+## Workflow
+0. **Resolve the wiki root.** Run `node scripts/ensure-wiki.mjs --json` and use the returned
+   `wikiRoot` as the base for every read below — never assume `wiki/`. A local wiki resolves
+   instantly (no-op); a wiki whose `.lisa.config.json` declares `wiki.source.url` is mirrored and
+   refreshed transparently first. The script is offline-tolerant (it proceeds with the existing
+   mirror and warns rather than blocking), so freshness is guaranteed here and the caller never has
+   to think about it.
+1. Read `<wikiRoot>/index.md` to locate candidate pages; consult `<wikiRoot>/start-here.md` for orientation.
+2. Drill into the relevant synthesis pages and their cited source notes.
+3. Synthesize an answer. **Every claim cites its wiki page and/or source note.** If the wiki does not
+   support an answer, say so plainly rather than inventing one; suggest an `/ingest` that would fill
+   the gap. Only record the gap in `wiki/open-questions/` if the user explicitly asks (that is a
+   writeback — see step 4); never write it silently.
+4. **Writeback (opt-in only):** if — and only if — the user explicitly asks to persist new synthesis
+   discovered during the query, route it through the ingest pipeline so provenance/index/log/state
+   stay consistent, and log it as a `QUERY` operation. Never write back silently.
+
+## Rules
+- **Read-only by default.** No page edits, index/log changes, state advancement, or PRs unless the
+  user explicitly requests writeback.
+- Prefer the wiki's own content over outside knowledge; distinguish wiki-sourced facts from your own
+  reasoning.
+- Surface contradictions or stale claims you encounter as `/lint`-style findings rather than
+  silently picking one.
+
+## Related
+`lisa-wiki-ingest`, `lisa-wiki-lint`, `lisa-wiki-usage`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-query/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Query"
+short_description: "Answer a question from the LLM…"
+default_prompt:
+  - "Use $lisa-wiki-query: Answer a question from the LLM…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-setup/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: lisa-wiki-setup
+description: "Scaffold, repair, verify, or…"
+---
+
+# lisa-wiki-setup
+
+Bring a repo's `wiki/` into conformance with the canonical structure from
+`wiki/lisa-wiki.config.json`. Safe to re-run: it creates what is missing and repairs drift, but
+never overwrites human-authored content.
+
+## When to use
+- First-time setup of the wiki in a repo.
+- Repairing a wiki that fails `/doctor` structural checks.
+- Upgrading after a new `lisa-wiki` release (`--upgrade`): re-render the contract snapshot and run a
+  compatibility report before writing.
+- `--with-ci`: also install the optional GitHub Action validator (`ci/lisa-wiki-validate.yml`).
+
+## Workflow
+1. **Config.** Read `wiki/lisa-wiki.config.json`, or create it interactively. Ask for: `org`,
+   `displayName`, **`purpose`** (one paragraph — what this wiki is for), `mode`
+   (`embedded|wrapper|standalone|subdir`), `categories`, source layout, connectors, sensitivity,
+   `sourceRetention`, and the **README mode** (`rich` default | `stub` | `preserve` — always ask;
+   never select `stub` implicitly). If `staff` is absent, seed the **standard roster** (below) as the
+   default — every wiki gets the standard operating team unless the user opts out or edits it. Union
+   each role's owned categories into `config.categories`. Validate with `scripts/validate-config.mjs`.
+2. **Structure.** Scaffold the canonical tree per `schema/wiki-structure.schema.json`:
+   `wiki/{index.md, log.md, start-here.md, schema/, sources/, state/, staff/, <category dirs>}`.
+   Create only what is missing.
+3. **Contract.** Render `wiki/schema/llm-wiki-contract.md` from the plugin templates + config via
+   `scripts/render-contract.mjs`, stamping the `kernelVersion`. This snapshot keeps the wiki
+   self-describing without the plugin installed.
+4. **Gitignore.** Merge the lisa-wiki gitignore block into the project's `.gitignore` via
+   `scripts/ensure-gitignore.mjs`. The block (delimited by `# BEGIN: AI GUARDRAILS WIKI` /
+   `# END: AI GUARDRAILS WIKI`) covers transient per-session worktrees and Lisa backup snapshots
+   (`.claude/worktrees/`, `.codex/worktrees/`, `.lisabak/`). Idempotent: re-running produces no
+   diff once the block is present. The block coexists with the base lisa plugin's
+   `# BEGIN: AI GUARDRAILS` block — both can be installed without overwriting each other because
+   the copy-contents strategy keys on the marker suffix. Wiki-wrapper repos (mode `wrapper` /
+   `standalone`) typically don't enable the base lisa plugin, so this step is the only path by
+   which they get the worktree-ignore patterns.
+5. **Pointers.** Ensure `AGENTS.md` / `CLAUDE.md` point at the contract + plugin (thin pointers only).
+6. **Staff.** For each `config.staff[]` entry (the standard roster by default), generate the role's
+   `wiki/staff/<role>.md` page and its dual-runtime subagents by delegating to `lisa-wiki-add-role`
+   (running the subagents is out of scope).
+7. **README.** Apply the chosen README mode (ingest the old README first; `rich` keeps install/usage +
+   adds the onboarding line; `stub` is the minimal pointer; `preserve` leaves it).
+8. **Verify.** Run `lisa-wiki-doctor` and report the verdict + any blocking items.
+
+## Standard roster
+The default operating team seeded into `config.staff[]` for every new wiki (Chief of Staff plus six
+domain agents). Each role becomes a `wiki/staff/<id>.md` page and a dual-runtime subagent; the human
+owner talks to Chief, who routes to the others. Owned categories are unioned into `config.categories`.
+
+| id | role | owns (categories) | sensitivity |
+|---|---|---|---|
+| `chief` | Chief of Staff | `projects`, `decisions`, `playbooks`, `open-questions` | confidential |
+| `sally` | Sales | `sales` | internal |
+| `mark` | Marketing | `marketing` | internal |
+| `felix` | Finance | `finance` | confidential |
+| `casey` | Customer Success | `customers` | internal |
+| `parker` | People | `people` | confidential |
+| `lex` | Legal & Compliance | `legal` | confidential |
+
+Projects may add, remove, or rename roles afterward; the standard roster is the starting point, not a
+constraint.
+
+## Rules
+- Idempotent; re-running produces no spurious changes.
+- Never overwrite human content; only create/repair structure and the rendered snapshot. The README is
+  rewritten only after its old content has been ingested, and only per the chosen `readme.mode`.
+- Project-scoped only; never stage secrets/OAuth artifacts; honor `mode` safety (wrapper/standalone).
+
+## Related
+`lisa-wiki-add-role`, `lisa-wiki-doctor`, `lisa-wiki-migrate`, `lisa-wiki-usage`.

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-setup/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Setup"
+short_description: "Scaffold, repair, verify, or…"
+default_prompt:
+  - "Use $lisa-wiki-setup: Scaffold, repair, verify, or…."

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-setup-automations/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: lisa-wiki-setup-automations
+description: "Set up the recurring LLM Wiki…"
+allowed-tools: ["Skill", "Bash", "Read"]
+---
+
+# Set up LLM Wiki automations: $ARGUMENTS
+
+This skill is a **specification, not a script.** It tells the current runtime which recurring wiki
+automation to create, on what cadence, and with which command — and the runtime creates it with its
+**native** scheduling mechanism. Do **not** hand-template schedule files or write shell to create
+them; invoke the runtime's automation tool with the spec below.
+
+It is the wiki counterpart of the base `/lisa:setup-automations`. It is a **separate** skill because
+the wiki plugin (`lisa-wiki`) is standalone — it can be installed without the base Lisa plugin, in
+which case `/lisa:setup-automations` is not present to schedule ingest. The two skills are
+independent and use disjoint name prefixes, so running both is safe.
+
+## Runtime scheduler (branch on the current runtime)
+
+- **Codex** → create a Codex **automation** via the native automations mechanism (prefer the
+  `automation_update` tool over hand-writing `~/.codex/automations/<id>/automation.toml`; the TOML is
+  only its backing store). Set the execution environment to **local** so it runs on this
+  workstation. Scope it to a durable project automation checkout, not a transient task worktree: use
+  `${CODEX_HOME:-~/.codex}/worktrees/<project>-automation-main` when available, create or refresh
+  that checkout from the project's `origin` remote if needed, and verify `git -C <cwd> rev-parse
+  --is-inside-work-tree --is-bare-repository` reports `true` then `false` before saving the
+  automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
+  metadata is broken.
+- **Claude** → use **`/schedule`** to create a local recurring routine.
+- **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
+  state that scheduling is unavailable and stop.
+
+## Parameters
+
+- `cadence` (default **daily**) — how often the full ingest runs. Accepts `daily`, `weekly`, or an
+  `every-<n>-hours` form. Map to a Codex `rrule`: daily → `FREQ=DAILY;INTERVAL=1`; weekly →
+  `FREQ=WEEKLY;INTERVAL=1`; every N hours → `FREQ=HOURLY;INTERVAL=<n>`. On Claude, pass the
+  equivalent `/schedule` cadence. Default is **daily** (`FREQ=DAILY;INTERVAL=1`).
+
+## The automation to create
+
+The automation runs **one cycle** of the full wiki ingest and respects that command's own confirmation
+and commit/PR policy (never ask before running; run a full ingest across every enabled
+non-external-write source; commit/PR per the ingest skill's bookends; report the cycle summary).
+Before running the ingest, the automation must attempt to sync its checkout: fetch the default remote
+branch and rebase the current automation branch onto it (for the common GitHub case, `origin/main`).
+If the checkout is already on the default branch, fast-forward/rebase it to the remote default. A
+dirty working tree is not by itself a blocker: capture `git status --short --branch`, leave
+pre-existing changes untouched, and continue when sync and ingest can run without overwriting those
+paths. Abort only when Git reports an actual sync conflict or ingest would need to modify an
+already-dirty path; in that case leave existing queue/wiki state unchanged and report the exact
+conflicting path(s).
+
+| Automation | Command it runs | Cadence |
+|---|---|---|
+| **wiki-ingest** | `/lisa-wiki:ingest` (no argument → full ingest across all enabled sources) | once a day (or `cadence`) |
+
+**Naming + scope (so teardown is precise).** Name the automation with the stable prefix
+`lisa-wiki-auto-<project>-` (i.e. `lisa-wiki-auto-<project>-ingest`), where `<project>` identifies
+this repo, and scope each Codex automation to the durable project automation checkout described
+above. This prefix is deliberately distinct from the base `lisa-auto-<project>-` set so
+`/lisa-wiki:tear-down-automations` removes exactly this automation and never touches the base
+automations or any other project's. Use a project identifier stable across runs and distinct from
+other repos (qualify it, e.g. with the owner — don't rely on a bare repo basename that could
+collide).
+
+**Idempotent.** Re-running this skill updates the existing `lisa-wiki-auto-<project>-ingest`
+automation in place (same name) rather than creating a duplicate.
+
+## Conditions / guards
+
+- Create the automation only when this repo actually has an LLM Wiki — i.e. `wiki/` exists with a
+  `wiki/lisa-wiki.config.json`. If there is no configured wiki, **stop and report** that the wiki
+  must be set up first (run `/lisa-wiki:setup`); do not schedule ingest against a non-existent wiki.
+- If the runtime has no native scheduler, stop and report what's missing rather than guessing.
+- For Codex, if the durable checkout cannot be created, fetched, or verified as a non-bare Git work
+  tree, stop and report the checkout problem instead of creating an automation that will fail later.
+
+## Report
+
+List the automation created or updated (name, the command it runs, the resolved cadence), or report
+that it was skipped and why (no configured wiki / no runtime scheduler).

package/plugins/lisa-wiki/.codex-plugin/skills/lisa-wiki-setup-automations/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Wiki Setup Automations"
+short_description: "Set up the recurring LLM Wiki…"
+default_prompt:
+  - "Use $lisa-wiki-setup-automations: Set up the recurring LLM Wiki…."