Remove duplicated instructions

Author: magnesj

copilot-instructions.md

@@ -50,55 +50,6 @@ These documents contain the authoritative information about the project. Always
 - Follow snake_case naming convention
 - Keep code compatible with Python 3.8+
 
-### PDM System Patterns
-
-When working with PDM (Project Data Model) objects:
-
-1. **Field Access**: Always use `()` to access field values:
-   ```cpp
-   // Correct
-   QString name = m_myTextField();
-   
-   // Incorrect
-   QString name = m_myTextField;
-   ```
-
-2. **Scriptable Fields**: Use scriptable initialization for Python API:
-   ```cpp
-   CAF_PDM_InitScriptableField(&m_fieldName, "FieldName", defaultValue, "Display Name");
-   ```
-
-3. **UI Attributes**: Use modern `setAttribute` pattern:
-   ```cpp
-   m_field.uiCapability()->setAttribute( caf::PdmUiComboBoxEditor::Keys::ADJUST_WIDTH_TO_CONTENTS, true );
-   ```
-
-### Common Patterns
-
-#### Adding a new PDM field
-```cpp
-// In header (.h)
-caf::PdmField<QString> m_myField;
-
-// In source (.cpp) constructor
-CAF_PDM_InitScriptableField(&m_myField, "MyField", QString(), "Display Name");
-```
-
-#### Field validation
-```cpp
-m_percentage.setRange(0.0, 100.0);
-m_count.setMinValue(0);
-m_value.setMaxValue(1000);
-```
-
-#### GRPC method integration
-```cpp
-QString RimcClassName_method::classKeywordReturnedType() const
-{
-    return RimTargetClass::classKeywordStatic();
-}
-```
-
 ## When to Stop and Ask
 
 If you encounter any of these situations, stop and ask the developer: