feat: add project lifecycle status management

[ReinaMaze]

close #155

Add Project Lifecycle Status Management

Feature Description:
Implement comprehensive lifecycle status tracking for projects, allowing owners to signal project maturity, stability, and maintenance status beyond verification status. Projects now have five distinct lifecycle states reflecting their real-world status.

Motivation:
Projects evolve through different phases from active development through sunset. Verification status alone doesn't capture this lifecycle information. Lifecycle status allows:

• Consumers to understand project stability and activity level
• Owners to signal maintenance intent
• Indexers and UIs to filter and display appropriate projects
• Proper management of deprecated/sunset projects

Implementation:

New Types

• ProjectLifecycleStatus enum with 5 variants:
  • Active - regularly maintained, recommended for use
  • Beta - under active development, not yet stable
  • Paused - temporarily not maintained
  • Deprecated - no longer recommended for new use
  • Sunset - officially discontinued

Core Changes

1. Types (src/types.rs):

   • Added ProjectLifecycleStatus enum with Clone, Copy, Debug, Eq, PartialEq
   • Added lifecycle_status: ProjectLifecycleStatus field to Project struct (defaults to Active)
   • Added lifecycle_status: Option<ProjectLifecycleStatus> to ProjectUpdateParams

2. Storage (src/storage_keys.rs):

   • Added ProjectLifecycleStatus(u64) storage key variant

3. Events (src/events.rs):

   • New ProjectLifecycleStatusUpdatedEvent struct with:
     • project_id, owner, previous_status, new_status, timestamp
   • New publish_project_lifecycle_status_updated_event() function
   • Emits on status changes with full audit trail

4. Contract Interface (src/lib.rs):

   • New public method: set_project_lifecycle_status(project_id, caller, status) - owner-only
   • New public method: list_projects_by_lifecycle_status(status, start_id, limit) - filters + pagination

5. Registry Logic (src/project_registry.rs):

   • Implementation of status update with authorization check
   • Implementation of filtered list with pagination (excludes archived projects)
   • Default lifecycle_status = Active on project registration

API Methods

set_project_lifecycle_status(project_id, caller, status) → Project

• Owner-only operation
• Validates project exists
• Emits event on status change
• Returns updated project
• Error: Unauthorized if not owner, ProjectNotFound if ID invalid

list_projects_by_lifecycle_status(status, start_id, limit) → Vec

• Filters projects by lifecycle status
• Excludes archived projects
• ID-based pagination (start_id is cursor, limit defaults to 100)
• Returns matching projects

Test Coverage (20 test cases)

• ✅ Project created with Active status
• ✅ Set status to Beta/Paused/Deprecated/Sunset
• ✅ Unauthorized users cannot change status
• ✅ Event emission verification
• ✅ Multiple sequential transitions
• ✅ List filtering by Active status
• ✅ List filtering by Beta status
• ✅ List pagination
• ✅ Archived projects excluded from lists
• ✅ Lifecycle status field in Project struct
• ✅ Non-owner rejection
• ✅ Status-unchanged optimization (no event if same)

Backward Compatibility

• ✅ Existing projects default to Active status
• ✅ No breaking changes to existing APIs
• ✅ Lifecycle status is optional in update params
• ✅ All existing tests continue to pass

Acceptance Criteria Met

• ✅ Project status enum - Five lifecycle states defined
• ✅ Owner can update - set_project_lifecycle_status() restricted to owner
• ✅ List APIs filter by status - list_projects_by_lifecycle_status() with pagination
• ✅ Status changes emit events - ProjectLifecycleStatusUpdatedEvent with audit trail
• ✅ Comprehensive tests - Valid statuses, transitions, filtering, authorization, events

Related Documentation:

• See CONTRACT_INTERFACE.md for API details
• See EVENTS_SCHEMA.md for event schema