Fix inconsistent sharing fields between ProjectSerializer and ProjectDetailSerializer

[Copilot]

ProjectDetailSerializer (used for retrieve) was missing share_token and is_shared, while ProjectSerializer (used for list/create) exposed both — making sharing status unavailable on the detail endpoint.

Changes

• ProjectDetailSerializer: Added share_token and is_shared to fields and read_only_fields, matching ProjectSerializer's contract

class ProjectDetailSerializer(serializers.ModelSerializer):
    class Meta:
        model = Project
        fields = [
            'id', 'name', 'description', 'framework',
            'share_token', 'is_shared',          # added
            'architecture', 'created_at', 'updated_at'
        ]
        read_only_fields = ['id', 'share_token', 'is_shared', 'created_at', 'updated_at']

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This PR fixes an API contract inconsistency where ProjectDetailSerializer (used for retrieve operations) was missing the share_token and is_shared fields that were already exposed in ProjectSerializer (used for list/create operations). This made sharing status unavailable when fetching project details.

Changes:

• Added share_token and is_shared to ProjectDetailSerializer.Meta.fields to match ProjectSerializer
• Added both fields to read_only_fields to prevent client modification (consistent with server-side sharing management)