feat: [CI-19005]: Updating LE for Pipeline Annotations.

feat: [CI-19005]: Updating LE logs.

feat: [CI-19005]: Adding Pipeline Service support from API

feat: [CI-19005]: Fixing annotations support.

feat: [CI-19005]: Fixing annotations support.

feat: [CI-19005]: Adding logs

feat: [CI-19005]: Adding Planexecutionid at CLI level using that for API

feat: [CI-19005]: Adding API logs

feat: [CI-19005]: Adding Annotations Config and new token.

feat: [CI-19005]: Adding Query Params.

feat: [CI-19005]: Updating Account Id.

feat: [CI-19005]: Final LE changes.

feat: [CI-19005]: Optimizations and Adding Annotations in LE.

feat: [CI-19005]: Adding Annotations folder in LE.

feat: [CI-19005]: Optimizing files.

feat: [CI-19005]: Updating structs and optimizing code.

feat: [CI-19005]: Optimizing files.

feat: [CI-19005]: Updating FF.

feat: [CI-19005]: Lint fixes.

feat: [CI-19005]: Adding retry logic.

feat: [CI-19005]: Removing logs and optimizing.

feat: [CI-19005]: Updating structure.

Author: DevanshMathur19

Annotations/README.md

@@ -0,0 +1,83 @@
+# Annotation CLI
+
+A CLI tool for creating and storing annotation properties in Harness CI/CD pipelines, similar to Buildkite's annotate functionality.
+
+## Features
+
+- **File-based summaries**: Reads markdown content from user-created files
+- **Execution context**: Automatically captures Harness environment variables
+- **Cross-platform**: Compatible with Linux, Mac, and Windows
+- **Multi-step support**: Single annotations.json file for multiple pipeline steps
+- **Append functionality**: Can append additional content to existing steps
+
+## Usage
+
+```bash
+./cli annotate --context "context-name" --summary "summary-file.md" [options]
+```
+
+### Required Parameters
+
+- `--context`: Context identifier (used as grouping key)
+- `--summary`: Path to markdown file containing summary content
+
+### Optional Parameters
+
+- `--style`: Annotation style (replaces existing value)
+- `--priority`: Priority level (default: 5, replaces existing value)
+
+### Environment Variables
+
+The CLI automatically reads these Harness environment variables:
+
+- `HARNESS_EXECUTION_ID`: Current execution ID
+- `HARNESS_STEP_ID`: Current step ID
+- `HARNESS_ACCOUNT_ID`: Account identifier
+- `HARNESS_PROJECT_ID`: Project identifier
+- `HARNESS_ANNOTATIONS_FILE`: If set, target path where the CLI writes annotations JSON
+
+## Examples
+
+### Basic annotation
+```bash
+./cli annotate --context "build-validation" --summary "test-results.md" --priority 8
+```
+
+### Append to existing context (in the same step)
+```bash
+# Reuse the same --context to append additional content within the same step
+./cli annotate --context "build-validation" --summary "additional-notes.md"
+```
+
+### With custom style
+```bash
+./cli annotate --context "deployment" --summary "deploy-results.md" --style "success" --priority 9
+```
+
+## Output Files
+
+- **annotations JSON**: Structured data containing all annotations and metadata. The output path is:
+  1. `HARNESS_ANNOTATIONS_FILE` environment variable (if set)
+  2. `./annotations.json` (default)
+- User-created **.md files**: Summary content files (not modified by CLI)
+
+### Notes on Step ID
+- The Harness step identifier is sourced from the environment and stored in `execution_context.harness_step_id`.
+- There is no separate `--stepid` argument; per-step annotations are written to a per-step file (via `HARNESS_ANNOTATIONS_FILE`), and context-based entries are merged within that file.
+
+## Build
+
+```bash
+go build -o cli main.go
+```
+
+For cross-platform builds:
+```bash
+# Linux
+GOOS=linux GOARCH=amd64 go build -o cli-linux main.go
+
+# Windows
+GOOS=windows GOARCH=amd64 go build -o cli-windows.exe main.go
+
+# macOS
+GOOS=darwin GOARCH=amd64 go build -o cli-macos main.go

Annotations/cli

@@ -0,0 +1,3 @@
+module annotate-cli
+
+go 1.21