131868bdca
Major security, observability, and configuration improvements:
## Security Hardening
- Implemented configurable CORS (no more wildcards)
- Added comprehensive auth middleware for admin endpoints
- Enhanced webhook HMAC validation
- Added input validation and rate limiting
- Security headers and CSP policies
## Configuration Management
- Made N8N webhook URL configurable (WHOOSH_N8N_BASE_URL)
- Replaced all hardcoded endpoints with environment variables
- Added feature flags for LLM vs heuristic composition
- Gitea fetch hardening with EAGER_FILTER and FULL_RESCAN options
## API Completeness
- Implemented GetCouncilComposition function
- Added GET /api/v1/councils/{id} endpoint
- Council artifacts API (POST/GET /api/v1/councils/{id}/artifacts)
- /admin/health/details endpoint with component status
- Database lookup for repository URLs (no hardcoded fallbacks)
## Observability & Performance
- Added OpenTelemetry distributed tracing with goal/pulse correlation
- Performance optimization database indexes
- Comprehensive health monitoring
- Enhanced logging and error handling
## Infrastructure
- Production-ready P2P discovery (replaces mock implementation)
- Removed unused Redis configuration
- Enhanced Docker Swarm integration
- Added migration files for performance indexes
## Code Quality
- Comprehensive input validation
- Graceful error handling and failsafe fallbacks
- Backwards compatibility maintained
- Following security best practices
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
12 lines
688 B
Go
12 lines
688 B
Go
// Package pgproto3 is an encoder and decoder of the PostgreSQL wire protocol version 3.
|
|
//
|
|
// The primary interfaces are Frontend and Backend. They correspond to a client and server respectively. Messages are
|
|
// sent with Send (or a specialized Send variant). Messages are automatically buffered to minimize small writes. Call
|
|
// Flush to ensure a message has actually been sent.
|
|
//
|
|
// The Trace method of Frontend and Backend can be used to examine the wire-level message traffic. It outputs in a
|
|
// similar format to the PQtrace function in libpq.
|
|
//
|
|
// See https://www.postgresql.org/docs/current/protocol-message-formats.html for meanings of the different messages.
|
|
package pgproto3
|