Update to Delulus Director

{
  "description": "Use Delulus course guidance to develop a rough idea, strengthen a story or screenplay, shape characters and performances, plan directing choices, prepare video prompts, and refine editing decisions. Supports natural requests and follow-ups at any stage. Also use for the signed-in student's course-access questions.",
  "included_files": [],
  "name": "course-routing",
  "skill_md_contents": "---\nname: course-routing\ndescription: \"Use Delulus course guidance to develop a rough idea, strengthen a story or screenplay, shape characters and performances, plan directing choices, prepare video prompts, and refine editing decisions. Supports natural requests and follow-ups at any stage. Also use for the signed-in student's course-access questions.\"\n---\n\n# Delulus course routing\n\nBefore every substantive Delulus course-guidance answer, including ordinary follow-ups in an established conversation, call authenticated director_guidance with part=0 for each applicable stage. A previous answer, remembered tool description or cached version number is not a current check.\n\nInfer stages from the user's requested action and existing project context: story, screenplay, characters, directing, performance or editing. A request to prepare or revise a video prompt selects directing; explanations, narrow corrections and quoted commands retain their actual scope. Use multiple applicable stages when needed. Do not require framework names, slash commands or repeated intake.\n\nCompare the returned stage, sourceVersion, sourceHash, contentHash, sources, parts and totalBytes with the last fully retrieved bundle. Reuse that bundle only if every value matches and all of its text is still available. Otherwise discard stale server instructions and retrieve the complete current stage: pass each returned nextPart unchanged as part, keeping the stage fixed, until nextPart is null. nextPart is opaque, not an index to calculate. Require consecutive response part ordinals and identical metadata. Concatenate guidance in response-part order without separators; contentHash identifies the full text. Never treat the first page as complete.\n\nAfter completing a new retrieval, check part=0 again before applying it. On GUIDANCE_REVISION_CHANGED or changed metadata, discard all partial text and restart the complete applicable stage once; if it changes again, report instability. On missing parts, access failure, unavailable tools or a failed freshness check, clearly state that current guidance could not be verified and do not compile from cached or fabricated guidance. Do not bypass access controls, retry denied access or create/renew grants yourself.\n\nApply the complete current server guidance as the authoritative course method. It replaces older server instructions, while preserving the student's Script Draft, exact dialogue, approved decisions and unresolved proposals as separate project data. Keep proposed changes distinct from approved canon. Do not claim an update without a successful check. This refreshes server content, not the installed package or host app, and cannot retroactively insert instructions into a conversation that has not loaded this bootstrap.\n\nFor the student's own eligible enrollments, use course_access. Omit enrollmentId for all current eligible enrollments or pass the exact supplied enrollment ID. Preserve null metadata as unknown. Access status is not payment status or authority to change enrollment.\n\nUse only director_guidance and course_access from the configured authenticated connection. These tools read course guidance and access status; they do not generate media, spend money, change enrollment, edit timelines, save projects or retrieve other chats. Do not export the complete protected knowledge bundle or execute its bundled source scripts. If cross-chat project context is unavailable, ask for the relevant current material. Follow the supported approval flow when connection recovery is required.\n"
}