[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75HZBJ04KWA4SWMRWKC7F2Q":3,"skill-same:01M75HZBJ04KWA4SWMRWKC7F2Q":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75HZBJ04KWA4SWMRWKC7F2Q","debug-stale-classification",null,"Diagnose why a necroflow RuleCall did or did not rerun using consumed hashes, invalidators, and forced invalidation.","MatteoLacki\u002Fnecroflow","MatteoLacki","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3964160?v=4","01M75HZ5XZX3Y0EBFWNS5N278P","Matteo","01M75HZ5Z2VGHESSAYCXRHETR6",1,"MIT","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdebug-stale-classification\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: debug-stale-classification\ndescription: Diagnose why a necroflow RuleCall did or did not rerun using consumed hashes, invalidators, and forced invalidation.\n---\n\n# Debugging necroflow cache classification\n\n## Ask live tools first\n\n```bash\nnecroflow explain job.toml\nnecroflow explain --node counts job.toml\nnecroflow explain --json job.toml\nnecroflow doctor job.toml\n```\n\nExplain reports RuleCalls in registration order with nested output Nodes. Reasons include `output_missing`, `up_to_date`, `parent_will_run`, `consumed_hash_missing`, `consumed_hash_other_hasher`, `parent_content_changed`, `parent_hash_unchecked`, `parent_undecided`, `dependency_metadata_missing_or_invalid`, `dependency_metadata_mismatch`, `forced_invalidation`, `invalidator_changed`, and `compromised_prior_state`.\n\n## Classification model\n\n`planning.py` classifies canonical RuleCalls, not individual output Nodes.\n\n1. Request closure starts from selected Nodes, then follows owning calls and `parent_calls`.\n2. Any missing declared co-output makes complete call `MISSING`.\n3. Non-`up_to_date` persisted state, forced call key, or changed output invalidator makes call `STALE`.\n4. A parent scheduled for execution also marks active descendants for replay by default. Every child still waits until all parents settle successfully.\n5. For every parent Node, compare recorded `dependencies.toml: consumed_hash` with current bytes.\n6. Missing or malformed consumed metadata is stale. Matching hashes preserve a cache when parents did not rerun, or when `reuse_unchanged=True` explicitly allows reuse after rebuilding them.\n7. Existing inactive call workdirs are listed in `plan.orphans`; they never run.\n8. Verdicts and reasons are in `plan.verdicts` \u002F `plan.reasons` from `plan_execution(dag)`, not on the RuleCall.\n\nCurrent hashes trust `.rip\u002F{filename}.hash` only while output mtime is no newer than hash-file mtime. Newer outputs are rehashed. External edits preserving or backdating mtime are unsupported.\n\n## Frequent causes\n\n- Different identity: command, config, contracts, shell path, or parent lineage changed. New path is missing; old path may be orphan.\n- Missing sibling: one absent co-output makes atomic call missing.\n- Missing consumed hash: legacy or malformed dependency metadata forces safe replay.\n- Parent rebuilt, child cached: `--reuse-unchanged` was enabled and output bytes were identical.\n- Parent rebuilt, child replayed: default cascading policy, changed output bytes, or another child cache check required replay.\n- Bare external path string: fingerprint includes path text, not external bytes. Ingest with `symlink(Type, path)`, use an invalidator, or include content in config.\n- Leftover `.rip\u002Fstate = running`: compromised call reruns (a crash or kill; a failure elsewhere no longer leaves running siblings unrecorded).\n- Constraints and `repeat`: execution policy, excluded from identity.\n\n## Force replay\n\n```bash\nnecroflow run --invalidate LABEL job.toml\nnecroflow run --reap NAME job.toml\n```\n\nPython:\n\n```python\ndag.run(forced_stale_call_keys={node.rule_call.relative_path})\n```\n\nForced labels do not add requirements.\n\n## Inspect metadata\n\n```text\n\u003Cworkdir>\u002F.rip\u002Fstate\n\u003Cworkdir>\u002F.rip\u002Fdependencies.toml\n\u003Cworkdir>\u002F.rip\u002F{filename}.hash\n\u003Cworkdir>\u002F.rip\u002F{filename}.invalidation\n\u003Cworkdir>\u002F.rip\u002Fjob.log\n\u003Cworkdir>\u002F.rip\u002Frun.toml\n\u003Cworkdir>\u002F.rip\u002Fgraph.tgf\n```\n","# Debugging necroflow cache classification\n\n## Ask live tools first\n\n```bash\nnecroflow explain job.toml\nnecroflow explain --node counts job.toml\nnecroflow explain --json job.toml\nnecroflow doctor job.toml\n```\n\nExplain reports RuleCalls in registration order with nested output Nodes. Reasons include `output_missing`, `up_to_date`, `parent_will_run`, `consumed_hash_missing`, `consumed_hash_other_hasher`, `parent_content_changed`, `parent_hash_unchecked`, `parent_undecided`, `dependency_metadata_missing_or_invalid`, `dependency_metadata_mismatch`, `forced_invalidation`, `invalidator_changed`, and `compromised_prior_state`.\n\n## Classification model\n\n`planning.py` classifies canonical RuleCalls, not individual output Nodes.\n\n1. Request closure starts from selected Nodes, then follows owning calls and `parent_calls`.\n2. Any missing declared co-output makes complete call `MISSING`.\n3. Non-`up_to_date` persisted state, forced call key, or changed output invalidator makes call `STALE`.\n4. A parent scheduled for execution also marks active descendants for replay by default. Every child still waits until all parents settle successfully.\n5. For every parent Node, compare recorded `dependencies.toml: consumed_hash` with current bytes.\n6. Missing or malformed consumed metadata is stale. Matching hashes preserve a cache when parents did not rerun, or when `reuse_unchanged=True` explicitly allows reuse after rebuilding them.\n7. Existing inactive call workdirs are listed in `plan.orphans`; they never run.\n8. Verdicts and reasons are in `plan.verdicts` \u002F `plan.reasons` from `plan_execution(dag)`, not on the RuleCall.\n\nCurrent hashes trust `.rip\u002F{filename}.hash` only while output mtime is no newer than hash-file mtime. Newer outputs are rehashed. External edits preserving or backdating mtime are unsupported.\n\n## Frequent causes\n\n- Different identity: command, config, contracts, shell path, or parent lineage changed. New path is missing; old path may be orphan.\n- Missing sibling: one absent co-output makes atomic call missing.\n- Missing consumed hash: legacy or malformed dependency metadata forces safe replay.\n- Parent rebuilt, child cached: `--reuse-unchanged` was enabled and output bytes were identical.\n- Parent rebuilt, child replayed: default cascading policy, changed output bytes, or another child cache check required replay.\n- Bare external path string: fingerprint includes path text, not external bytes. Ingest with `symlink(Type, path)`, use an invalidator, or include content in config.\n- Leftover `.rip\u002Fstate = running`: compromised call reruns (a crash or kill; a failure elsewhere no longer leaves running siblings unrecorded).\n- Constraints and `repeat`: execution policy, excluded from identity.\n\n## Force replay\n\n```bash\nnecroflow run --invalidate LABEL job.toml\nnecroflow run --reap NAME job.toml\n```\n\nPython:\n\n```python\ndag.run(forced_stale_call_keys={node.rule_call.relative_path})\n```\n\nForced labels do not add requirements.\n\n## Inspect metadata\n\n```text\n\u003Cworkdir>\u002F.rip\u002Fstate\n\u003Cworkdir>\u002F.rip\u002Fdependencies.toml\n\u003Cworkdir>\u002F.rip\u002F{filename}.hash\n\u003Cworkdir>\u002F.rip\u002F{filename}.invalidation\n\u003Cworkdir>\u002F.rip\u002Fjob.log\n\u003Cworkdir>\u002F.rip\u002Frun.toml\n\u003Cworkdir>\u002F.rip\u002Fgraph.tgf\n```\n",{"name":5,"description":7},"main","3e33cb65c9af13a7acc2f5bb67401118fb7bc8e4",".claude\u002Fskills\u002Fdebug-stale-classification",0,"https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow","https:\u002F\u002Fgithub.com\u002FMatteoLacki","No Bio, go Mech.","2026-11-11 13:24:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MatteoLacki\u002Fnecroflow --skill debug-stale-classification",{"tool":38,"command":39},"bunx","bunx skills add MatteoLacki\u002Fnecroflow --skill debug-stale-classification",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MatteoLacki\u002Fnecroflow --skill debug-stale-classification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdebug-stale-classification\u002FSKILL.md",true,[],[47,54,61,66,73],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M75HZQ3QM78KEGFEEDTXEJ1H","use-necroflow","Write, inspect, run, and debug downstream Necroflow pipelines with typed artifacts, Python workflows, and job TOMLs. Use when creating or operating a Necroflow workflow; framework internals have separate contributor guidance.","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002Fsrc\u002Fnecroflow\u002Fskills\u002Fuse-necroflow\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M75HZM61XFRA1BT0D59Z93T1","write-a-scheduler","How to write a custom necroflow RuleCall scheduler using current three-argument protocol.","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-a-scheduler\u002FSKILL.md",[],[],{"skillNo":62,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75HZJSD4127JA0T1BFX1ZR6","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fuse-necroflow\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75HZE54RH6Q4J26H1PKET7C","necroflow-style","necroflow coding style for AI agents — invariants and anti-patterns derived from the git history. Load before writing or refactoring necroflow source code.","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnecroflow-style\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75HZ8SEXWSA1XHQBG7D7PCS","add-a-rule","How to declare a necroflow rule correctly — command decorators, built-in file rules, placeholders, typed outputs, and common mistakes.","https:\u002F\u002Fgithub.com\u002FMatteoLacki\u002Fnecroflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-a-rule\u002FSKILL.md",[],[]]