etherweave-load-context

To initialize a new Cursor session, load the Etherweave master context by triggering a three-part load sequence: Part A for the core prompt and index, Part B for rules and references, and Part C for cursor and agents.

Recovering a coherent workspace after a context reset requires reloading the master system prompt and rules in their canonical order. This enforces the original session alignment and restores the structured three-part context sequence.

Yes, the Etherweave context loader requires the SKILL.md frontmatter to be present in the workspace. Without this file, the canonical load sequence cannot validate and apply the master prompts and rules.

Session context times out due to platform constraints, and reapplying master rules requires triggering the canonical context load. This restores the workspace state by reloading the core prompt, rules, and agent configurations.

Yes, you can use split-loading for context management in large Cursor sessions. It applies the three-part master context sequentially with per-part confirmations, ensuring the workspace initializes without exceeding context limits.