Skip to main content

PROJECT_INSTRUCTIONS_NOT_APPLIED_WARNING

Constant PROJECT_INSTRUCTIONS_NOT_APPLIED_WARNING 

Source
pub(crate) const PROJECT_INSTRUCTIONS_NOT_APPLIED_WARNING: &str = "components.projectInstructions: recorded for reference, never installed — these files belong to the importing repository, not to the bundle. Inspect them with agent.project_instructions and apply anything you want deliberately";
Expand description

The exact warning parse_bundle_import_with_budget pushes when components.memory is present — ABF v0.2 §2.3. A shared constant (rather than a literal duplicated at both the push site and bundle_import_for_agent_impl’s filter site, reagent P1 PR #2527) so the two can never drift apart: if this message ever changes, the filter in bundle.rs keeps working because it references the same constant, not a copy of the string. Warning for an ABF carrying components.projectInstructions.

Phase 3 of SPEC_INSTRUCTION_AND_MEMORY_PORTABILITY_2026_09_09.md. These entries record what the source agent was reading. They are surfaced and never installed — the files they describe belong to whatever repository the bundle is being imported into, and an import that wrote them would be doing what SPEC_CLAUDE_MD_OWNERSHIP_PROTECTION_2026_08_22.md exists to prevent.

Unlike MEMORY_COMPONENT_IGNORED_WARNING this has no filter site: memory warns only on the agent-less path because bundle.import_for_agent really does install it, whereas no import path installs these. The warning is therefore unconditional and permanent, not a “use the other RPC” pointer.