@bluefly/openstandardagents 0.1.9 → 0.2.5-RC

package/.kiro/specs/website-design-audit/requirements.md

@@ -0,0 +1,199 @@
+# Requirements Document: OSSA Website Design System Audit & Enhancement
+
+## Introduction
+
+This document outlines requirements for a comprehensive design system audit and enhancement of the Open Standard Agents (OSSA) website. The audit identifies critical issues in brand consistency, visual hierarchy, component architecture, accessibility, and user experience that must be addressed to achieve a premium, professional standard befitting an industry specification.
+
+## Glossary
+
+- **Design System**: The complete collection of reusable components, patterns, tokens, and guidelines that define the visual and interaction language
+- **Component Library**: The set of reusable UI components (buttons, cards, navigation, etc.)
+- **Design Tokens**: Centralized variables for colors, typography, spacing, and other design primitives
+- **Visual Hierarchy**: The arrangement and presentation of elements to guide user attention and comprehension
+- **Accessibility (a11y)**: Design and development practices ensuring usability for people with disabilities (WCAG 2.1 AA compliance)
+- **Responsive Design**: Layouts that adapt gracefully across device sizes and orientations
+- **Information Architecture**: The structural design of information spaces to support findability and understanding
+- **Cognitive Load**: The mental effort required to use an interface
+- **Atomic Design**: Design methodology organizing components from atoms → molecules → organisms → templates → pages
+
+## Requirements
+
+### Requirement 1: Brand Identity & Visual Consistency
+
+**User Story:** As a visitor, I want a cohesive visual experience across all pages, so that I perceive OSSA as a professional, trustworthy standard.
+
+#### Acceptance Criteria
+
+1. WHEN viewing any page THEN the Website SHALL apply consistent brand colors from the centralized SCSS variables across all components
+2. WHEN encountering gradients THEN the Website SHALL use the defined gradient system (gradient-brand, gradient-hero, gradient-button) without deviation
+3. WHEN viewing logos and brand assets THEN the Website SHALL display them with consistent sizing, spacing, and treatment
+4. WHEN navigating between pages THEN the Website SHALL maintain visual continuity through consistent header, footer, and navigation patterns
+5. WHEN viewing semantic colors (success, warning, error, info) THEN the Website SHALL apply the muted palette defined in _variables.scss
+
+### Requirement 2: Typography System & Readability
+
+**User Story:** As a reader, I want clear, scannable content with proper typographic hierarchy, so that I can quickly find and understand information.
+
+#### Acceptance Criteria
+
+1. WHEN viewing headings THEN the Website SHALL implement a clear 6-level hierarchy (H1-H6) with distinct size, weight, and spacing
+2. WHEN reading body text THEN the Website SHALL maintain line-height between 1.5-1.75 for optimal readability
+3. WHEN viewing code examples THEN the Website SHALL use the JetBrains Mono font with appropriate syntax highlighting
+4. WHEN encountering long-form content THEN the Website SHALL limit line length to 65-75 characters for comfortable reading
+5. WHEN viewing text on colored backgrounds THEN the Website SHALL ensure WCAG AA contrast ratios (4.5:1 minimum for body text, 3:1 for large text)
+
+### Requirement 3: Component Architecture & Reusability
+
+**User Story:** As a developer maintaining the site, I want a well-organized component library, so that I can build new pages efficiently without duplicating code.
+
+#### Acceptance Criteria
+
+1. WHEN creating new UI elements THEN the System SHALL provide atomic components (Button, Card, Badge, etc.) with clear prop interfaces
+2. WHEN styling components THEN the System SHALL use Tailwind utility classes composed into semantic component classes
+3. WHEN building complex layouts THEN the System SHALL compose molecules from atoms following atomic design principles
+4. WHEN adding interactive elements THEN the System SHALL provide consistent hover, focus, and active states
+5. WHEN implementing forms THEN the System SHALL provide validated input components with error states
+
+### Requirement 4: Spacing & Layout System
+
+**User Story:** As a designer, I want consistent spacing and layout patterns, so that pages feel harmonious and professionally crafted.
+
+#### Acceptance Criteria
+
+1. WHEN applying spacing THEN the System SHALL use a consistent scale (4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px, 96px)
+2. WHEN creating sections THEN the System SHALL apply consistent vertical rhythm with section padding (py-12, py-16, py-20, py-24)
+3. WHEN building grids THEN the System SHALL use consistent gap values (gap-4, gap-6, gap-8) based on content density
+4. WHEN designing containers THEN the System SHALL use max-width constraints (max-w-4xl, max-w-6xl, max-w-7xl) for readability
+5. WHEN stacking elements THEN the System SHALL maintain consistent margin-bottom values within content blocks
+
+### Requirement 5: Navigation & Information Architecture
+
+**User Story:** As a user, I want intuitive navigation that helps me find information quickly, so that I don't get lost or frustrated.
+
+#### Acceptance Criteria
+
+1. WHEN viewing the header THEN the System SHALL display primary navigation with clear visual hierarchy and active states
+2. WHEN on mobile devices THEN the System SHALL provide an accessible hamburger menu with smooth transitions
+3. WHEN navigating documentation THEN the System SHALL provide a persistent sidebar with section organization
+4. WHEN viewing breadcrumbs THEN the System SHALL show the current location within the site hierarchy
+5. WHEN searching THEN the System SHALL provide instant feedback and relevant results
+
+### Requirement 6: Interactive Elements & Micro-interactions
+
+**User Story:** As a user, I want responsive, delightful interactions, so that the interface feels polished and professional.
+
+#### Acceptance Criteria
+
+1. WHEN hovering over buttons THEN the System SHALL provide smooth transitions (transition-all duration-300) with visual feedback
+2. WHEN clicking interactive elements THEN the System SHALL provide immediate visual confirmation
+3. WHEN loading content THEN the System SHALL display skeleton screens or loading states
+4. WHEN encountering errors THEN the System SHALL display clear, actionable error messages
+5. WHEN completing actions THEN the System SHALL provide success feedback through toast notifications or inline messages
+
+### Requirement 7: Accessibility & Inclusive Design
+
+**User Story:** As a user with disabilities, I want an accessible website, so that I can navigate and understand content regardless of my abilities.
+
+#### Acceptance Criteria
+
+1. WHEN navigating with keyboard THEN the System SHALL provide visible focus indicators on all interactive elements
+2. WHEN using screen readers THEN the System SHALL provide semantic HTML with proper ARIA labels and landmarks
+3. WHEN viewing images THEN the System SHALL include descriptive alt text for all meaningful images
+4. WHEN encountering color-coded information THEN the System SHALL provide additional non-color indicators
+5. WHEN viewing forms THEN the System SHALL associate labels with inputs and provide clear error messages
+
+### Requirement 8: Responsive Design & Mobile Experience
+
+**User Story:** As a mobile user, I want a seamless experience on my device, so that I can access information on-the-go.
+
+#### Acceptance Criteria
+
+1. WHEN viewing on mobile THEN the System SHALL adapt layouts using mobile-first responsive breakpoints
+2. WHEN interacting on touch devices THEN the System SHALL provide touch targets of at least 44x44px
+3. WHEN viewing tables THEN the System SHALL make them horizontally scrollable or stack on mobile
+4. WHEN viewing navigation THEN the System SHALL collapse to a mobile-friendly menu
+5. WHEN viewing images THEN the System SHALL serve appropriately sized images for the viewport
+
+### Requirement 9: Performance & Optimization
+
+**User Story:** As a user, I want fast page loads, so that I don't wait unnecessarily for content.
+
+#### Acceptance Criteria
+
+1. WHEN loading pages THEN the System SHALL achieve Lighthouse performance scores above 90
+2. WHEN loading images THEN the System SHALL use next/image with lazy loading and optimization
+3. WHEN loading fonts THEN the System SHALL use font-display: swap to prevent FOIT
+4. WHEN rendering components THEN the System SHALL minimize layout shifts (CLS < 0.1)
+5. WHEN loading JavaScript THEN the System SHALL code-split and lazy-load non-critical bundles
+
+### Requirement 10: Content Presentation & Scannability
+
+**User Story:** As a busy professional, I want scannable content with clear visual hierarchy, so that I can quickly find what I need.
+
+#### Acceptance Criteria
+
+1. WHEN viewing long-form content THEN the System SHALL break text into digestible chunks with subheadings
+2. WHEN scanning pages THEN the System SHALL use visual anchors (icons, badges, colors) to guide attention
+3. WHEN viewing lists THEN the System SHALL use appropriate list styles (bullets, numbers, checkmarks) for content type
+4. WHEN encountering important information THEN the System SHALL use callout boxes or highlighted sections
+5. WHEN viewing code examples THEN the System SHALL provide syntax highlighting and copy buttons
+
+### Requirement 11: Homepage Hero & First Impression
+
+**User Story:** As a first-time visitor, I want to immediately understand what OSSA is, so that I can decide if it's relevant to me.
+
+#### Acceptance Criteria
+
+1. WHEN landing on homepage THEN the System SHALL display a clear value proposition above the fold
+2. WHEN viewing the hero THEN the System SHALL use the gradient system with legible white text
+3. WHEN scanning the hero THEN the System SHALL provide 3-5 key benefits with visual icons
+4. WHEN ready to act THEN the System SHALL display prominent CTAs (Get Started, View Docs, GitHub)
+5. WHEN scrolling THEN the System SHALL reveal content with subtle animations for engagement
+
+### Requirement 12: Documentation Pages & Code Examples
+
+**User Story:** As a developer, I want clear documentation with working code examples, so that I can implement OSSA quickly.
+
+#### Acceptance Criteria
+
+1. WHEN viewing docs THEN the System SHALL provide a persistent sidebar with section navigation
+2. WHEN reading code examples THEN the System SHALL display syntax-highlighted code with copy buttons
+3. WHEN viewing API references THEN the System SHALL organize information in scannable tables or cards
+4. WHEN encountering complex concepts THEN the System SHALL provide diagrams or visual aids
+5. WHEN needing more context THEN the System SHALL link to related documentation sections
+
+### Requirement 13: Playground & Interactive Tools
+
+**User Story:** As a user learning OSSA, I want interactive tools to experiment, so that I can learn by doing.
+
+#### Acceptance Criteria
+
+1. WHEN using the playground THEN the System SHALL provide a Monaco editor with YAML syntax highlighting
+2. WHEN validating manifests THEN the System SHALL display clear success/error states with actionable feedback
+3. WHEN switching templates THEN the System SHALL provide visual indicators for the active template
+4. WHEN viewing validation results THEN the System SHALL highlight specific errors with line numbers
+5. WHEN downloading manifests THEN the System SHALL provide one-click download and copy functionality
+
+### Requirement 14: Footer & Secondary Navigation
+
+**User Story:** As a user, I want comprehensive footer navigation, so that I can find additional resources and information.
+
+#### Acceptance Criteria
+
+1. WHEN viewing the footer THEN the System SHALL organize links into logical categories (Docs, Resources, Community)
+2. WHEN looking for social links THEN the System SHALL display GitHub, npm, and other relevant platforms
+3. WHEN viewing legal information THEN the System SHALL display copyright and license information
+4. WHEN on mobile THEN the System SHALL stack footer columns vertically for readability
+5. WHEN viewing the footer THEN the System SHALL use muted colors (gray-900 background) for visual separation
+
+### Requirement 15: Logo Integration & Brand Assets
+
+**User Story:** As a visitor, I want to see consistent, professional logo usage, so that I recognize the OSSA brand.
+
+#### Acceptance Criteria
+
+1. WHEN viewing partner logos THEN the System SHALL display them in grayscale with consistent sizing
+2. WHEN hovering over logos THEN the System SHALL provide subtle hover effects (scale, color)
+3. WHEN viewing the OSSA logo THEN the System SHALL display it with the gradient text treatment
+4. WHEN on mobile THEN the System SHALL scale logos appropriately for smaller screens
+5. WHEN loading logos THEN the System SHALL use optimized SVG or WebP formats

package/.prettierignore

@@ -0,0 +1,7 @@
+
+node_modules
+dist
+build
+coverage
+*.min.js
+*.min.css

package/.prettierrc.json

@@ -0,0 +1,10 @@
+{
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false,
+  "semi": true,
+  "singleQuote": true,
+  "trailingComma": "es5",
+  "bracketSpacing": true,
+  "arrowParens": "always"
+}

package/.redocly.yaml

@@ -1,63 +1,9 @@
-# Redocly configuration for OSSA API documentation
-apiDefinitions:
-  main:
-    root: src/api/ossa-complete.openapi.yml
-  specification:
-    root: src/api/specification.openapi.yml
-  acdl:
-    root: src/api/acdl-specification.yml
-  clean-architecture:
-    root: src/api/clean-architecture.openapi.yml
-  mcp:
-    root: src/api/mcp-infrastructure.openapi.yml
-  orchestration:
-    root: src/api/orchestration.openapi.yml
+extends:
+  - recommended
 
-lint:
-  extends:
-    - recommended
-  rules:
-    operation-operationId: error
-    operation-summary: error
-    tag-description: warning
-    info-description: warning
-    no-server-example.com: error
-    no-unused-components: warning
-    
-theme:
-  colors:
-    primary:
-      main: '#2196F3'
-    success:
-      main: '#4CAF50'
-    warning:
-      main: '#FF9800'
-    error:
-      main: '#F44336'
-    
-  logo:
-    gutter: '20px'
-    
-  typography:
-    fontSize: '16px'
-    fontFamily: '"Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif'
-    
-  codeBlock:
-    backgroundColor: '#263238'
-    
-features.openapi:
-  showConsole: true
-  hideTryItPanel: false
-  hideDownloadButton: false
-  disableSearch: false
-  expandResponses: '200,201'
-  jsonSampleExpandLevel: 3
-  hideSchemaTitles: false
-  simpleOneOfTypeLabel: false
-  sortPropsAlphabetically: false
-  payloadSampleIdx: 0
-  
-seo:
-  title: 'OSSA - Open Standards for Scalable Agents'
-  description: 'Official API documentation for OSSA v0.1.9 specification'
-  keywords: 'OSSA, AI agents, API, OpenAPI, scalable agents, orchestration'
+rules:
+  no-server-example.com: off
+  no-required-schema-properties-undefined: error
+  operation-operationId: error
+  tag-description: warn
+  info-contact: warn

package/.releaserc.json

@@ -0,0 +1,85 @@
+{
+  "branches": [
+    "main",
+    {
+      "name": "development",
+      "prerelease": "dev"
+    }
+  ],
+  "plugins": [
+    [
+      "@semantic-release/commit-analyzer",
+      {
+        "preset": "conventionalcommits",
+        "releaseRules": [
+          { "type": "feat", "release": "minor" },
+          { "type": "fix", "release": "patch" },
+          { "type": "perf", "release": "patch" },
+          { "type": "revert", "release": "patch" },
+          { "type": "docs", "release": "patch" },
+          { "type": "chore", "release": false },
+          { "type": "refactor", "release": "patch" },
+          { "type": "test", "release": false },
+          { "type": "build", "release": false },
+          { "type": "ci", "release": false },
+          { "breaking": true, "release": "major" }
+        ],
+        "parserOpts": {
+          "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"]
+        }
+      }
+    ],
+    [
+      "@semantic-release/release-notes-generator",
+      {
+        "preset": "conventionalcommits",
+        "presetConfig": {
+          "types": [
+            { "type": "feat", "section": "✨ Features", "hidden": false },
+            { "type": "fix", "section": "🐛 Bug Fixes", "hidden": false },
+            { "type": "perf", "section": "⚡ Performance", "hidden": false },
+            { "type": "revert", "section": "⏪ Reverts", "hidden": false },
+            { "type": "docs", "section": "📚 Documentation", "hidden": false },
+            { "type": "refactor", "section": "♻️ Code Refactoring", "hidden": false },
+            { "type": "test", "section": "✅ Tests", "hidden": true },
+            { "type": "build", "section": "🏗️ Build System", "hidden": true },
+            { "type": "ci", "section": "👷 CI/CD", "hidden": true },
+            { "type": "chore", "section": "🔧 Chores", "hidden": true }
+          ]
+        }
+      }
+    ],
+    [
+      "@semantic-release/changelog",
+      {
+        "changelogFile": "CHANGELOG.md",
+        "changelogTitle": "# Changelog\n\nAll notable changes to OSSA (Open Standard for Scalable AI Agents) will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),\nand this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)."
+      }
+    ],
+    [
+      "@semantic-release/npm",
+      {
+        "npmPublish": true,
+        "tarballDir": "dist"
+      }
+    ],
+    [
+      "@semantic-release/gitlab",
+      {
+        "gitlabUrl": "https://gitlab.com",
+        "assets": [
+          { "path": "dist/*.tgz", "label": "Distribution Package" },
+          { "path": "CHANGELOG.md", "label": "Changelog" }
+        ],
+        "successComment": "🎉 This ${issue.pull_request ? 'MR is included' : 'issue has been resolved'} in version ${nextRelease.version}\n\nThe release is available on:\n- [npm package](https://www.npmjs.com/package/@bluefly/openstandardagents)\n- [GitLab release](${releases[0].url})\n- [Documentation](https://openstandardagents.org)\n\nYour **${issue.pull_request ? 'merge request' : 'issue'}** is included in this release!"
+      }
+    ],
+    [
+      "@semantic-release/git",
+      {
+        "assets": ["CHANGELOG.md", "package.json", "package-lock.json"],
+        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+      }
+    ]
+  ]
+}

package/.version.json

@@ -0,0 +1,6 @@
+{
+  "current": "0.2.5-RC",
+  "latest_stable": "0.2.4",
+  "spec_path": "spec/v{version}",
+  "schema_file": "ossa-{version}.schema.json"
+}

package/CHANGELOG.md

@@ -0,0 +1,196 @@
+# Changelog
+
+All notable changes to OSSA (Open Standard for Scalable AI Agents) will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [v0.2.5-RC] - 2025-11-26
+
+### Added
+
+- **ossa run command**: New CLI command to execute agents using the OpenAI adapter
+  - Interactive REPL mode for ongoing conversations
+  - Single message mode with `-m, --message` flag
+  - Verbose output with `-v, --verbose` flag for debugging
+  - Configurable max turns with `--max-turns` option
+  - Runtime selection with `-r, --runtime` flag (currently supports OpenAI)
+  - Validation toggle with `--no-validate` flag
+  - Comprehensive error handling and user-friendly messages
+
+- **OpenAI Adapter**: Complete runtime adapter for OpenAI API integration
+  - OpenAI function calling API support
+  - Tool registration and execution with custom handlers
+  - Conversation history management
+  - Model selection from manifest or OpenAI extensions
+  - System prompt configuration
+  - Tool mapping from OSSA capabilities to OpenAI functions
+  - Temperature and max tokens configuration
+  - Max turns limit to prevent infinite loops
+
+- **Documentation**:
+  - Complete CLI reference for `ossa run` command
+  - Comprehensive OpenAI adapter guide
+  - Enhanced running agents guide with troubleshooting
+  - README.md updated with run command examples
+
+- **Examples**:
+  - Basic OpenAI agent example (`examples/openai/basic-agent.ossa.yaml`)
+  - Advanced multi-tool agent example (`examples/openai/multi-tool-agent.ossa.json`)
+
+- **Tests**:
+  - Unit tests for run command
+  - Unit tests for OpenAI adapter
+  - Integration tests for CLI execution
+
+### Changed
+
+- Enhanced getting started documentation with detailed option descriptions
+- Updated README.md with running agents section
+
+## [0.2.4](https://github.com/blueflyio/openstandardagents/compare/v0.2.3...v0.2.4) (2025-11-19)
+
+### Package Rename
+
+- **IMPORTANT**: Package renamed from `@bluefly/open-standards-scalable-agents` to `@bluefly/openstandardagents`
+- The old package `@bluefly/open-standards-scalable-agents` has been deprecated
+- Update your dependencies: `npm install @bluefly/openstandardagents`
+
+### Website Fixes
+
+- Fixed 100+ broken links (gitlab.com → github.com/blueflyio/openstandardagents)
+- Fixed npm registry auth in CI pipeline
+- Standardized all package references across documentation
+- Fixed broken internal links (/docs/deployment, /research, CLI-Reference)
+- Updated all schema version references to v0.2.3
+- Fixed RSS feed base URL to openstandardagents.org
+
+## [0.2.3](https://github.com/blueflyio/openstandardagents/compare/v0.2.2...v0.2.3) (2025-11-12)
+
+### Documentation
+
+- **spec**: Created versioned release structure in spec/v0.2.3/ with schema, README, CHANGELOG, and migration guide
+- **examples**: Enhanced inline documentation for kAgent and integration pattern examples
+- **migrations**: Added comprehensive migration guide from v0.2.2 to v0.2.3 (no breaking changes)
+- **compatibility**: Documented backward compatibility with v0.2.2
+
+### Features
+
+- **schema**: Added v0.2.3 schema support with backward compatibility for v0.2.2
+- **types**: Extended SchemaVersion type to include '0.2.3'
+- **repository**: Updated SchemaRepository to load v0.2.3 schema files
+- **validation**: Set v0.2.3 as default version for validation service
+
+### Bug Fixes
+
+- **git**: Cleaned up diverged branches (merged main → development)
+- **tags**: Removed erroneous v0.3.0 tag from repository
+- **versions**: Reset all version references to 0.2.3 (removed v2.0.0 confusion)
+
+### BREAKING CHANGES
+
+**None** - This is a fully backward-compatible patch release. All v0.2.2 manifests work without modification.
+
+## [2.0.0](https://github.com/blueflyio/openstandardagents/compare/v1.0.0...v2.0.0) (2025-11-05)
+
+### Bug Fixes
+
+- add v0.2.2 schema JSON files to git ([7ad617a](https://github.com/blueflyio/openstandardagents/commit/7ad617a5bcdb2304e4aaa9424562fa1654d90fb4))
+- add v0.2.2 schema support and set as default ([da22d4d](https://github.com/blueflyio/openstandardagents/commit/da22d4d47d4e9cc732c33290f971c670647d3318))
+- all tests pass with v0.2.2 format ([ee00098](https://github.com/blueflyio/openstandardagents/commit/ee00098772bbb9b6c128b483dce0366ce983329c))
+- change releases to manual triggers on main branch only ([7d48895](https://github.com/blueflyio/openstandardagents/commit/7d4889515c85107c9ca56cb624ebe70846af6041))
+- complete ESM module support with proper .js extensions ([b9754f3](https://github.com/blueflyio/openstandardagents/commit/b9754f384cde11640860ceb3370b8180c290c2b8))
+- convert ES module syntax in convert-to-kagent.js ([dba2b37](https://github.com/blueflyio/openstandardagents/commit/dba2b37c3992545b0230e6ae0458a0c215c54852))
+- convert ES module syntax in convert-to-kagent.js ([9b00af6](https://github.com/blueflyio/openstandardagents/commit/9b00af64966ea0a2a2183ecbcd4b2837767968f0))
+- convert release.config.js to ES module syntax ([b9cacbf](https://github.com/blueflyio/openstandardagents/commit/b9cacbfda385234034f6afb19925c6884bacb3cc))
+- correct version from 1.0.0 to 0.3.0 ([1786934](https://github.com/blueflyio/openstandardagents/commit/178693428cf72d8bdc216ddfd65d111ec41f811f))
+- correct version to 0.2.1 (patch bump) ([4227258](https://github.com/blueflyio/openstandardagents/commit/42272581065db0fc3bf30b3f4fd65a27af0dfd93))
+- disable promote-to-main job - use merge requests for main branch ([76e4e0b](https://github.com/blueflyio/openstandardagents/commit/76e4e0b6284ca346dd9768e827bbb5c083226a5c))
+- **ci:** make promote-to-main fast-forward-only; auto-create MR on conflicts via API ([a414db0](https://github.com/blueflyio/openstandardagents/commit/a414db0d5fda70d499ef9e55162f499a39d029a8))
+- **ci:** make promote-to-main script a single multiline string to satisfy YAML parsing ([c1563ea](https://github.com/blueflyio/openstandardagents/commit/c1563eae6a90365db699f5e3c63e9268ec79e1dd))
+- **ci:** promote-to-main handles shallow clones and unrelated histories; add auth remote ([7a66d60](https://github.com/blueflyio/openstandardagents/commit/7a66d60142541505d0a65d0d5413adc34c24a235))
+- **ci:** remove colon from commit message to fix YAML parsing ([260270a](https://github.com/blueflyio/openstandardagents/commit/260270a24ce59752aef963a293b62b26e2c996c0))
+- **ci:** remove invalid need on promote-to-main (cannot need later-stage job) ([211dbf7](https://github.com/blueflyio/openstandardagents/commit/211dbf7cd38e3ffc4dac3ced00cf320754f815f1))
+- **ci:** remove stray text and update development branch git config ([eb895b5](https://github.com/blueflyio/openstandardagents/commit/eb895b580ab27cf84bc005340eeff43ce6c2bb6c))
+- **ci:** rename job to avoid YAML colon parsing issue ([f641574](https://github.com/blueflyio/openstandardagents/commit/f6415745b4423636d332915e9061e948142a3959))
+- replace all gitlab.com references with new instance ([89496c7](https://github.com/blueflyio/openstandardagents/commit/89496c7fa1e723491482f4c804fd9addf0da65f8))
+- update GitLab instance references ([b8480a6](https://github.com/blueflyio/openstandardagents/commit/b8480a6d089c790f1d4f17359f9c79951239824e))
+- revert to version 0.2.2 and fix schema validation ([5789f6d](https://github.com/blueflyio/openstandardagents/commit/5789f6d7bfa0cc8638307902701ac967579097b0))
+- schema formatting ([3dd018b](https://github.com/blueflyio/openstandardagents/commit/3dd018b56756da1821658a4a7ee8986e55c4b632))
+- update all tests for v0.2.2 format ([34bb695](https://github.com/blueflyio/openstandardagents/commit/34bb695bd2376b9d93d47d6867bf8b1f4a4e4b73))
+- update CHANGELOG version to 0.3.0 ([b10b9f4](https://github.com/blueflyio/openstandardagents/commit/b10b9f4c38ece7455995ccd96a28d4cfedf4df36))
+- **ci:** update Node.js version to 22 for semantic-release compatibility ([eef4b89](https://github.com/blueflyio/openstandardagents/commit/eef4b89de9e4ef4cf3361a9e95d30ee81e706e78))
+- update version to 0.2.2 and reorganize spec directory ([5f9a8a0](https://github.com/blueflyio/openstandardagents/commit/5f9a8a0f3d7fa6386d88e07da70c5fd775812bc8))
+- **aiflow:** URGENT - Reduce CPU requests from 500m to 50m ([846c8fd](https://github.com/blueflyio/openstandardagents/commit/846c8fda3861120d6324ce957bf33b03fa484826))
+- **ci:** use PRIVATE-TOKEN with CI_JOB_TOKEN for MR API; reuse existing MR if present ([afd8c25](https://github.com/blueflyio/openstandardagents/commit/afd8c258b635c519bd0698adb8972e1c09e6efe4))
+- validate command supports both v0.2.2 and v1.0 formats ([4d777d0](https://github.com/blueflyio/openstandardagents/commit/4d777d08ab49267ad8670acaf8d0fdfb3617cfb9))
+
+### chore
+
+- clean up OSSA for npm publication ([f6d2c27](https://github.com/blueflyio/openstandardagents/commit/f6d2c27b3ac972cf065bfe4d67cf1d9e51f47b51))
+
+### Features
+
+- add CryptoSage AIFlow social agent example ([9c03a6b](https://github.com/blueflyio/openstandardagents/commit/9c03a6b94f0741a56e1aaaefebd71d387f428235))
+- add CryptoSage AIFlow social agent example ([36a1a21](https://github.com/blueflyio/openstandardagents/commit/36a1a219d546bf29185c4df7218a844e5891a70c))
+- add ecosystem tasks orchestrator agent ([276b868](https://github.com/blueflyio/openstandardagents/commit/276b868722d46ed1198f3a7ffc1f37e815d82d3b))
+- add ecosystem tasks orchestrator agent ([b9ac082](https://github.com/blueflyio/openstandardagents/commit/b9ac082f2746107de11ebddba26fcc0e5c065ea0))
+- add kagent.dev and AIFlow-Agent bridge support to OSSA 1.0 ([c83f462](https://github.com/blueflyio/openstandardagents/commit/c83f46270cf7264dbe6b7a3936373a6568f6015e))
+- add kagent.dev and AIFlow-Agent bridge support to OSSA 1.0 ([2a98c1e](https://github.com/blueflyio/openstandardagents/commit/2a98c1ebd09eb7d34992dee44074073f070f89bf))
+- **ci:** add manual merge-to-main button after successful pipeline ([d3fb40c](https://github.com/blueflyio/openstandardagents/commit/d3fb40c5d1aef7bda5cac15d0c2215cfc3f77a37))
+- **ci:** add manual promotion and release buttons ([c57fb66](https://github.com/blueflyio/openstandardagents/commit/c57fb66e3f258a0ae87c51db9d6f2c1d7d9cdff2))
+- **ossa:** add OpenAI Agents SDK bridge extension ([3cf4c9f](https://github.com/blueflyio/openstandardagents/commit/3cf4c9fd5ae6c042a96c5ec328d514bacd8936c9))
+- add OpenAPI/Swagger specification extensions for AI agents ([bfe5025](https://github.com/blueflyio/openstandardagents/commit/bfe5025a83d06449648cd3e92588568bc42217c8))
+- **compliance:** Add OSSA reasoning compliance extension schema for chain-of-thought auditing ([9bb60ec](https://github.com/blueflyio/openstandardagents/commit/9bb60ecc20b56df65f0e3d5e8562104386b773d7))
+- **automation:** Add resource validation to prevent cluster exhaustion ([3910b66](https://github.com/blueflyio/openstandardagents/commit/3910b662905661504e57969bc4d76b6c87282dbc))
+- add semantic-release for automated versioning ([589d530](https://github.com/blueflyio/openstandardagents/commit/589d5304c8e1b5a59d3ba0b15a809a961acc4e7e))
+- complete OSSA ecosystem automation suite ([cbef539](https://github.com/blueflyio/openstandardagents/commit/cbef539551430f7710cf689f50ea0aad4c8d3bb2))
+- complete OSSA ecosystem automation suite ([abc485f](https://github.com/blueflyio/openstandardagents/commit/abc485fc00344a3fe405739b734d8807cdf9adc2))
+- complete OSSA v0.2.2 agent migration with framework integration ([b0ab662](https://github.com/blueflyio/openstandardagents/commit/b0ab662f31faafed8de01e2ffb4a5a8c948eb634))
+- Complete OSSA v1.0 TypeScript implementation with Drupal integration ([be27188](https://github.com/blueflyio/openstandardagents/commit/be271880728e4dc6f164b4c85af432daf3d66858))
+- **aiflow:** Complete Phases 2 & 3 - Production-ready AIFlow integration ([0f81e9d](https://github.com/blueflyio/openstandardagents/commit/0f81e9d0c77586241caf94e593ad738481c0f68d)), closes [#1876](https://github.com/blueflyio/openstandardagents/issues/1876) [#1877](https://github.com/blueflyio/openstandardagents/issues/1877) [#1878](https://github.com/blueflyio/openstandardagents/issues/1878)
+- Complete platform integration - OpenAPI + Helm for all projects ([d7140aa](https://github.com/blueflyio/openstandardagents/commit/d7140aac1e780d6094ef5aa20cf31c9adf3072d6))
+- Enhanced OSSA CLI with audit, inspect, and schema commands ([ca21cc2](https://github.com/blueflyio/openstandardagents/commit/ca21cc271161f592dd39a9e4bd7d7f3fd97a0004)), closes [#178](https://github.com/blueflyio/openstandardagents/issues/178)
+- integrate v1.0 to v0.2.2 migration into OSSA CLI ([349c4dd](https://github.com/blueflyio/openstandardagents/commit/349c4ddda10066a628447fff6a62edc09615e3be))
+- **kagent:** intelligent agent deployment + ecosystem tooling ([b602d25](https://github.com/blueflyio/openstandardagents/commit/b602d25e9b200e01ff07be1fdf95a09da5938cb6))
+- intelligent agent deployment with resource optimization ([e9fba1e](https://github.com/blueflyio/openstandardagents/commit/e9fba1eedab9dcc6c5e0674a192bdf5315152984))
+- mass cleanup and standardization - ZERO ERRORS ([79cb19d](https://github.com/blueflyio/openstandardagents/commit/79cb19d1e8b7b0454a25abf9a8e18d765aae5fd8))
+- mass cleanup and standardization - ZERO ERRORS ([cd6f1cc](https://github.com/blueflyio/openstandardagents/commit/cd6f1cc5278c74bde5b1ad63e71d8665e0bb26a4))
+- mass cleanup and standardization - ZERO ERRORS ([3452f4f](https://github.com/blueflyio/openstandardagents/commit/3452f4f3c2b0a9d9ac72ac2c6917a4bda5ac050c))
+- **spec:** organize OSSA spec with clean v1.0 versioning ([08468e3](https://github.com/blueflyio/openstandardagents/commit/08468e3831fa8dc8e83bc2bbfdae352ab3f33e10))
+- OSSA v0.1.9 with kAgent extension support ([1d4c0b5](https://github.com/blueflyio/openstandardagents/commit/1d4c0b50cdcb5d4bf2fcc3f648968688f3139517))
+- **aiflow:** Phase 2 - BuildKit registration, Phoenix tracing, integration tests ([ee7279d](https://github.com/blueflyio/openstandardagents/commit/ee7279db63cee7afe4be2a2b044d87b40778f0f4)), closes [#1876](https://github.com/blueflyio/openstandardagents/issues/1876)
+- **aiflow:** Phase 3 - K8s deployment, load testing, CI/CD, monitoring ([f5b9f46](https://github.com/blueflyio/openstandardagents/commit/f5b9f46ddea9fc90910a773093d620813a5945b1)), closes [#1877](https://github.com/blueflyio/openstandardagents/issues/1877)
+- **aiflow:** Phase 3 - Production deployment, load testing, monitoring ([6066100](https://github.com/blueflyio/openstandardagents/commit/60661001e698edf269c4b4d2a450dc36090c0935)), closes [#1877](https://github.com/blueflyio/openstandardagents/issues/1877)
+- **aiflow:** Phase 4 - SLO/SLA, incident response, chaos engineering ([3fb78f1](https://github.com/blueflyio/openstandardagents/commit/3fb78f15a25e9cf700e8e61bf68c088652afc066)), closes [#1878](https://github.com/blueflyio/openstandardagents/issues/1878)
+- update k6 load testing scenarios ([e0bfc15](https://github.com/blueflyio/openstandardagents/commit/e0bfc1550962e8357fd446f23babdec7ff7634ef))
+
+### BREAKING CHANGES
+
+- None - this is additive functionality
+- Manual version management replaced with semantic-release
+- Cleaned up project structure for v1.0.0 release
+- - Removed old Jest config and legacy tests
+
+* Removed helm charts (moved to agent-buildkit)
+* CLI now uses TypeScript compiled output
+
+Test Results: 68/68 passing, 97.85% coverage
+Status: Production Ready
+
+- - CLI now requires OSSA 1.0 manifest format
+
+* Production example updated to OSSA 1.0 spec
+
+New Features:
+
+- audit command: Score agents 0-100 on completeness, best practices, security, performance
+- inspect command: Detailed agent information with --json output
+- schema command: Query schema attributes (roles, protocols, compliance, bridges)
+- Fixed ES module conflicts in CLI
+
+Improvements:
+
+- Production example validates with 80/100 audit score
+- All required fields properly enforced
+- Comprehensive validation output