/wbContext — Live Demo ()
What /wbContext would actually produce on wb-labs right now. The packages, conventions, and parked items below are real.
1. Live target
| Field | Live value |
|---|---|
| Workspace root | /home/wissemb11/Allprojects/wb-labs/ (not a package — would refuse direct /wbContext) |
| Most-mature package | core2/packages/wb-core/ (would produce richest context) |
| Untested / parked packages | core2/packages/wbc-ui2-cdn/, others (per wbc-ui2-tech-debt.md) |
| Sibling packages | core2/packages/wb-dataviewer/, core2/packages/wbc-ui2-cdn/, core2/packages/wbc-ui2/, others |
| Existing context.md files | None obvious in core2/packages/*/.agents/workflows/ (would be created on first /wbContext per package) |
| Memory available | 12 leaf files, including the conventions and parked-items entries |
The fourth row is the key one: the workspace has multiple packages, none with a current context.md. /wbContext is most useful at the start of a session that's going to dig into a specific package.
2. What each input form would resolve to today
| Input | Live resolution |
|---|---|
/wbContext (from wb-labs root) | Halt. Refuses; suggests /wbContext core2/packages/wb-core/ or similar. |
/wbContext core2/packages/wb-core/ | Produces full broad context. ~200 lines. |
/wbContext core2/packages/wbc-ui2-cdn/ | Produces context with a prominent "PARKED TECH DEBT" section per memory. |
/wbContext core2/packages/wb-dataviewer/ | Includes the apiResponse_ memory note + flagging the no-invalidation gap. |
/wbContext --focus="docs_v4_sync" | Cross-references the transmission spec + project_docs_edition.md. Useful for the current session. |
/wbContext --scope="global" | Lightweight navigation file: where each package lives, which depends on which, top-level conventions. |
/wbContext --focus="dev gating __WBC_DEV__" --scope="cross-package" | Cross-references WBC_DEV across all packages. Includes staleness warning. |
3. Per-flag behavior, applied live
| Flag combination | Live result |
|---|---|
| (no flag) | Broad context for the target package. |
--focus="X" | Focused context file (context_X_<date>.md) alongside any existing broad context. |
--scope="cross-package" | Multi-package read; staleness warning header. |
--scope="global" | Lightweight; navigation only. |
--refresh | Force re-scan even if existing context.md looks current. |
--refresh --focus="X" | Force re-build of the focused file. |
4. Pipelines
/wbContext Live Execution Simulator
First context for wb-core (the most useful invocation right now)
/wbContext core2/packages/wb-core/> /wbContext core2/packages/wb-core/[SYSTEM] Target: core2/packages/wb-core/
[SCAN] Reading package.json, vite.config.js, src/, tests/...
[MEMORY] Cross-referencing: feedback_wbCode_dev_only.md,
feedback_wbCode_rule.md, feedback_model_selection.md,
wbc-ui2-tech-debt.md (sibling parked items),
project_pkg_dist_mismatch.md (sibling parked items)
[WRITE] core2/packages/wb-core/.agents/workflows/context.md
# Context: core2/packages/wb-core/
## Identity
Package: @wbc-ui2/wb-core
Role: Core component library — exports WBCode, WBCodeSlot, WBC.js
orchestrator, tier-enforcement utilities, renderString.
Position: foundational. Consumed by every other core2/ package.
Owner conventions: @wbc-ui2 npm ecosystem maintained by Wissem.
## Tech stack
- Vue 3 (composition API, no Options API in new code)
- Vite for dev + build
- Vitest for unit tests
- TypeScript pragmatically; not strict-mode
## Dependencies
- vue ^3.4
- (no sibling @wbc-ui2/* deps — wb-core is the foundation)
## Conventions
- **Dev gating**: __WBC_DEV__ 3-mode pattern (full / dev / hidden).
Source: feedback_wbCode_dev_only.md.
- **wbCode rule in examples**: every example uses :wbCode="false"
(collapsed by default; toggle exposed).
Source: feedback_wbCode_rule.md.
- **Model declaration**: the agent 4 (simple) or the agent 4 (complex)
declared before action. JWT/auth work is the agent.
Source: feedback_model_selection.md.
## Active plan
- reports/<date>/plans/plan_wb-core_20260504.md
- Row 1: JWT handshake in tierEnforcement.js — ⬜
- Row 2: renderString escape pass — ⬜
- Row 3: WBC.js decomposition — ⬜ (DAG-blocked by 1, 2)
## Recent activity
None this session — current work is in frontEnd/wbc-ui/core2/packages/wb-flow/templates/, not in this
package.
## What NOT to touch
- WBC.js decomposition (row 3 of plan): DAG-blocked AND awaits
architectural conversation. Don't refactor blindly.
- Sibling packages have parked items that should NOT propagate here:
- wbc-ui2-cdn: dist-folder mismatch (don't mirror the convention).
- wbc-ui2: vuepress crash, untested apps (don't add untested code
here as "consistent").
## Entry points
- src/index.js: central re-exports
- src/components/WBCode.vue: code-display component (dev-gated)
- src/components/WBCodeSlot.vue: slot-based variant (dev-gated)
- src/tierEnforcement.js: gatekeeper for privileged ops
- src/renderString.js: HTML-escape utility (subject of plan row 2)
[OK] Context written. /wbExplain can now use this as substrate.
💠 Pipeline First context for wb-core (the most useful invocation right now)
💠 Pipeline A focused context for the current docs work
💠 Pipeline The "global" navigation snapshot
5. What would refuse today
| Trigger | Live response |
|---|---|
/wbContext from wb-labs root | Halt. Suggests pointing at a package. |
/wbContext frontEnd/wbc-ui/core2/packages/wb-flow/templates/ | Halt. frontEnd/wbc-ui/core2/packages/wb-flow/templates/ is documentation, not a package. Suggests /wbContext --focus="docs_v4_sync" or similar. |
/wbContext core2/packages/some-nonexistent/ | Halt. No package.json. |
/wbContext --focus="" | Halt. Empty focus is meaningless. |
/wbContext core2/ | Halt — multiple packages inside. Asks user to pick one. |
/wbContext --scope="global" (re-run) | Permitted; would write a fresh global file with a more recent date. |
/wbContext core2/packages/wb-core/ re-run with no changes since last context | Notice: "context appears current; re-running anyway with --refresh? [y/N]" |
The pattern: /wbContext produces a state snapshot scoped narrowly by default and refuses coarse scopes that produce fragile output. It cross-references memory for parked items and conventions, surfaces "what NOT to touch" as a first-class section, and treats global scope as navigation-only. The output is a file the next session reads — everything in it should still be true tomorrow or be marked as time-sensitive.